Execute any SQL statement (INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, etc.). Use with caution!
AI agents call execute_sql to permanently remove resources in LocalDB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool explicitly supports DDL and DML operations including DROP and DELETE, which are irreversible. Since it allows arbitrary SQL execution including destructive operations like DROP TABLE/DATABASE, it must be classified at the highest severity. The 'Use with caution!' warning from the tool author confirms awareness of the danger. Per the rules, Destructive takes precedence over Execute and Write.
From the tool's definition Execute any SQL statement (INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, etc.). Use with caution!
Attacks that exploit this kind of access
Execute any SQL statement (INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, etc.). Use with caution!. It is categorised as a Destructive tool in the LocalDB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LocalDB MCP Server MCP server in PolicyLayer and add a rule for execute_sql: 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 LocalDB MCP Server. Nothing to install.
execute_sql 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_sql 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_sql. 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_sql is provided by the LocalDB MCP Server MCP server (sam2332/localdb-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 →