AI agents call policy_engine_delete to permanently remove resources in AWS Labs MySQL MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete' suffix in the tool name indicates an irreversible destructive action. Even without a full description, policy deletion is a serious operation that cannot be easily undone. The severity is 'high' rather than 'critical' because the actual scope and permissions required are unclear from the empty description; if this affects security policies across AWS infrastructure, it could be 'critical'.
From the tool's definition Tool name 'policy_engine_delete' contains 'delete', which indicates irreversible data removal. Description is empty, limiting ability to confirm exact scope, but the naming convention strongly suggests a destructive operation on policy engine data or policies.
Documented attack patterns abuse exactly the kind of access policy_engine_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs MySQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for policy_engine_delete:
{
"version": "1",
"default": "deny",
"hide": [
"policy_engine_delete"
]
}policy_engine_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
policy_engine_delete. It is categorised as a Destructive tool in the AWS Labs MySQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS Labs MySQL MCP Server MCP server in PolicyLayer and add a rule for policy_engine_delete: 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 AWS Labs MySQL MCP Server. Nothing to install.
policy_engine_delete 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 policy_engine_delete 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 policy_engine_delete. 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.
policy_engine_delete is provided by the AWS Labs MySQL MCP Server MCP server (awslabs.mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Labs MySQL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 AWS Labs MySQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.