Execute any SQL command (INSERT, UPDATE, DELETE, CREATE, etc.)
AI agents call execute_sql to permanently remove resources in Mcp Database — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permits arbitrary SQL execution including destructive statements like DELETE, DROP TABLE, TRUNCATE, and irreversible schema changes. Since it spans Execute, Write, and Destructive categories, the most severe applicable category is Destructive. Blast radius is critical: a misused command could wipe entire databases, drop schemas, or corrupt data irreversibly across any supported database type.
From the tool's definition "Execute any SQL command (INSERT, UPDATE, DELETE, CREATE, etc.)" — explicitly supports DELETE, DROP (implied by CREATE/any), and other irreversible DDL/DML operations
Attacks that exploit this kind of access
Execute any SQL command (INSERT, UPDATE, DELETE, CREATE, etc.). It is categorised as a Destructive tool in the Mcp Database MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Database 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 Mcp Database. 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 Mcp Database MCP server (nam088/mcp-database-server). 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 →