AI agents call delete to permanently remove resources in AWS HealthOmics MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'delete' unambiguously indicates a destructive action that irreversibly removes data. While the empty description reduces confidence slightly, the function name itself is definitive—delete operations cannot be undone and represent the highest risk category after financial impacts. Given this is a health data management system, the blast radius is significant if an agent misuses this tool.
From the tool's definition Tool is named 'delete' with no description provided. In the context of AWS HealthOmics MCP server (which manages genomic and health data), a delete operation is irreversible and removes data that cannot be recovered.
Documented attack patterns abuse exactly the kind of access delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS HealthOmics MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete:
{
"version": "1",
"default": "deny",
"hide": [
"delete"
]
}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.
delete. It is categorised as a Destructive tool in the AWS HealthOmics MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS HealthOmics MCP Server MCP server in PolicyLayer and add a rule for 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 HealthOmics MCP Server. Nothing to install.
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 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 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.
delete is provided by the AWS HealthOmics MCP Server MCP server (awslabs.aws-healthomics-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS HealthOmics 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 HealthOmics MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.