Critical Risk →

delete_access_key

delete_access_key

How to control delete_access_key ↓

What delete_access_key does on AWS Bedrock AgentCore MCP Server

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

Critical Risk

Why delete_access_key needs a policy

Deleting an access key removes authentication credentials permanently and cannot be undone. This is a destructive action with significant blast radius—a deleted key cannot be recovered, breaking applications or users relying on it. While not directly financial, it ranks above Execute because the action is irreversible and impacts security posture.

From the tool's definition Tool name is 'delete_access_key' with empty description. The verb 'delete' combined with 'access_key' (a critical AWS authentication credential) indicates irreversible removal of a secret.

Documented attack patterns abuse exactly the kind of access delete_access_key gives an agent:

How to control delete_access_key

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Bedrock AgentCore MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_access_key:

policy.json
{
  "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.

  1. Create a free account and register AWS Bedrock AgentCore MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_access_key

What does the delete_access_key tool do? +

delete_access_key. It is categorised as a Destructive tool in the AWS Bedrock AgentCore 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 delete_access_key? +

Register the AWS Bedrock AgentCore 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 AWS Bedrock AgentCore MCP Server. Nothing to install.

What risk level is delete_access_key? +

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.

Can I rate-limit delete_access_key? +

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.

How do I block delete_access_key completely? +

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.

What MCP server provides delete_access_key? +

delete_access_key is provided by the AWS Bedrock AgentCore MCP Server MCP server (awslabs.amazon-bedrock-agentcore-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AWS Bedrock AgentCore MCP Server tool call.

Start from AWS Bedrock AgentCore 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 Bedrock AgentCore MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.