AI agents invoke execute-query to trigger actions in Sql. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes arbitrary SQL code whose effects depend entirely on the SQL provided by the AI agent. While the 'safe' mode restricts to SELECT (Read), the tool's default capability spans Write (INSERT/UPDATE/DELETE) and potentially Destructive (DROP, TRUNCATE) operations in 'full' mode.
From the tool's definition Tool name 'execute-query' with description stating it executes SQL queries with modes ranging from SELECT-only to unrestricted ('full: all'). The 'write' mode explicitly permits INSERT/UPDATE/DELETE, and 'full' mode allows any SQL operation.
Attacks that exploit this kind of access
Execute a SQL query. Operations allowed depend on SQL_MCP_MODE (safe: SELECT only, write: +INSERT/UPDATE/DELETE, full: all). It is categorised as a Execute tool in the Sql MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Sql MCP server in PolicyLayer and add a rule for execute-query: 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.
execute-query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the execute-query 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 execute-query. 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.
execute-query 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 →