AI agents call delete_study 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 tool name 'delete_study' strongly suggests permanent deletion of study records. While the empty description limits confidence, the 'delete' verb places this in the Destructive category. In a healthcare/research context (AWS Labs MySQL), deleting a study likely removes data irreversibly.
From the tool's definition Tool name is 'delete_study' with no description provided. The name explicitly indicates a destructive operation (delete).
Documented attack patterns abuse exactly the kind of access delete_study 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 delete_study:
{
"version": "1",
"default": "deny",
"hide": [
"delete_study"
]
}delete_study 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.
delete_study. 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 delete_study: 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.
delete_study 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 delete_study 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 delete_study. 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.
delete_study 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.