Execute any SQL query (INSERT, UPDATE, DELETE, etc.)
AI agents call execute_query to permanently remove resources in SQLite MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool allows execution of arbitrary SQL, which spans Write, Execute, and Destructive categories. Because it explicitly supports DELETE and any SQL statement (including DDL like DROP), the most severe applicable category is Destructive. An AI agent could irreversibly delete or overwrite entire tables or databases, making the blast radius critical.
From the tool's definition 'Execute any SQL query (INSERT, UPDATE, DELETE, etc.)' — explicitly supports DELETE and arbitrary SQL, including potentially DROP TABLE or other irreversible operations
Attacks that exploit this kind of access
Execute any SQL query (INSERT, UPDATE, DELETE, etc.). It is categorised as a Destructive tool in the SQLite MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SQLite MCP Server 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 SQLite MCP Server. Nothing to install.
execute_query is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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 SQLite MCP Server MCP server (sam2332/mcp-quick-sqlite3). 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 →