AI agents call delete_access_key to permanently remove resources in Amazon ECS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting an access key is an irreversible action that cannot be undone. Once deleted, the access key is permanently removed and cannot be recovered. This falls squarely into the Destructive category. Severity is high because unauthorized deletion of access keys could disrupt legitimate AWS service operations, though the blast radius is more limited than if the tool could delete multiple resources or infrastructure.
From the tool's definition Tool name is 'delete_access_key', which indicates irreversible deletion of AWS access credentials. The description is empty, but the name unambiguously specifies a destructive operation.
Documented attack patterns abuse exactly the kind of access delete_access_key gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon ECS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_access_key:
{
"version": "1",
"default": "deny",
"hide": [
"delete_access_key"
]
}delete_access_key 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_access_key. It is categorised as a Destructive tool in the Amazon ECS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Amazon ECS MCP Server MCP server in PolicyLayer and add a rule for delete_access_key: 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 Amazon ECS MCP Server. Nothing to install.
delete_access_key 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_access_key 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_access_key. 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_access_key is provided by the Amazon ECS MCP Server MCP server (awslabs.ecs-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon ECS 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 Amazon ECS MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.