execute · MySQL MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute does on MySQL MCP Server

AI agents call execute to permanently remove resources in MySQL MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

WHY IT NEEDS A POLICY

Why execute needs a policy

The tool explicitly supports DELETE statements, which are irreversible data removal operations. While INSERT and UPDATE are Write-level, the inclusion of DELETE (and potentially DROP/TRUNCATE via arbitrary SQL execution) elevates this to Destructive.

From the tool's definition 执行INSERT/UPDATE/DELETE等数据修改语句 — explicitly supports DELETE operations alongside INSERT/UPDATE

Attacks that exploit this kind of access

Questions about execute

What does the execute tool do? +

执行INSERT/UPDATE/DELETE等数据修改语句. It is categorised as a Destructive tool in the MySQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on execute? +

Register the MySQL MCP Server MCP server in PolicyLayer and add a rule for execute: 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 MySQL MCP Server. Nothing to install.

What risk level is execute? +

execute is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit execute? +

Yes. Add a rate_limit block to the execute 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.

How do I block execute completely? +

Set action: deny in the PolicyLayer policy for execute. 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.

What MCP server provides execute? +

execute is provided by the MySQL MCP Server MCP server (microsnow/mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.