AI agents use connect-database to create or update resources in Sql — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sql environment.
This is a Write action because it creates and modifies connection state—a reversible change. It's not a Read action since it has side effects beyond data retrieval. Severity is medium because while connection manipulation itself is relatively benign, establishing unauthorized or malicious database connections could enable downstream data exfiltration or modification attacks, but the blast radius is bounded by…
From the tool's definition The tool modifies connection state by establishing a new database connection and disconnecting any existing one. While it doesn't directly modify data, it creates a persistent connection that enables subsequent database operations.
Attacks that exploit this kind of access
Connect to a database server (MSSQL, PostgreSQL, or SQLite). Disconnects any existing connection first. It is categorised as a Write tool in the Sql MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sql MCP server in PolicyLayer and add a rule for connect-database: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Sql. Nothing to install.
connect-database is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the connect-database rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for connect-database. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
connect-database is provided by the Sql MCP server (nakiriyuuzu/sql-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →