# Cursor

The Cursor use case starts with an incident: a Cursor agent with database access runs an ALTER TABLE in production, or writes destructive queries against a live schema. Civic scopes Cursor's database access to read-only by default. It can read schemas and run SELECT queries, but cannot alter tables, drop indexes, or write data unless you explicitly grant it. The page shows how to connect Cursor to Civic via MCP configuration, set guardrails on each connected tool, and verify that destructive operations are blocked and logged. Every query Cursor runs is captured in the audit trail.

Source: https://www.civic.com/use-cases/cursor