Execute a write SQL statement (INSERT / UPDATE / DELETE / ALTER / CREATE / DROP, etc).
AI agents call execute_sql to permanently remove resources in Mcp Mysql Explorer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool explicitly supports DROP, DELETE, and ALTER statements — all of which can irreversibly destroy or overwrite data. DROP and TRUNCATE are unrecoverable without backups, making this Destructive at critical severity. The open-ended 'etc' further implies arbitrary DDL/DML execution, giving an AI agent full destructive access to the database.
From the tool's definition Execute a write SQL statement (INSERT / UPDATE / DELETE / ALTER / CREATE / DROP, etc)
Attacks that exploit this kind of access
Execute a write SQL statement (INSERT / UPDATE / DELETE / ALTER / CREATE / DROP, etc). It is categorised as a Destructive tool in the Mcp Mysql Explorer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Mysql Explorer 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 Mysql Explorer. 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 Mysql Explorer MCP server (xsg22/mcp-mysql-explorer). 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 →