Critical Risk →

delete_access_key

delete_access_key

How to control delete_access_key ↓

What delete_access_key does on Amazon Bedrock Knowledge Base Retrieval MCP Server

AI agents call delete_access_key to permanently remove resources in Amazon Bedrock Knowledge Base Retrieval 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 is irreversible and destructive. An AI agent misusing this tool could permanently revoke authentication credentials, causing service outages, account lockouts, or privilege escalation opportunities if an attacker's credentials were targeted. This has the highest blast radius among the destructive class of operations.

From the tool's definition Tool name is 'delete_access_key' which performs irreversible deletion of AWS IAM access credentials. The description is empty, but the name unambiguously indicates deletion of sensitive authentication material.

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 Amazon Bedrock Knowledge Base Retrieval 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 Amazon Bedrock Knowledge Base Retrieval 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 Amazon Bedrock Knowledge Base Retrieval 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 Amazon Bedrock Knowledge Base Retrieval 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 Bedrock Knowledge Base Retrieval 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 Amazon Bedrock Knowledge Base Retrieval MCP Server MCP server (awslabs.bedrock-kb-retrieval-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 Amazon Bedrock Knowledge Base Retrieval MCP Server tool call.

Start from Amazon Bedrock Knowledge Base Retrieval 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 Bedrock Knowledge Base Retrieval 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.