AI agents call policy_delete to permanently remove resources in AWS DynamoDB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The 'delete' action is inherently destructive and irreversible. Removing IAM policies in AWS has immediate, permanent effects on system permissions and security posture. This is the most severe category applicable. High confidence despite empty description because the tool name itself is explicit, and the AWS DynamoDB/IAM policy context is clear from sibling tools.
From the tool's definition Tool name 'policy_delete' with 'delete' suffix indicates irreversible deletion operation. The AWS context (DynamoDB MCP Server) and sibling tools including 'add_inline_policy' and 'add_user_to_group' confirm this operates on AWS IAM policies, which are…
Documented attack patterns abuse exactly the kind of access policy_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS DynamoDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for policy_delete:
{
"version": "1",
"default": "deny",
"hide": [
"policy_delete"
]
}policy_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.
policy_delete. It is categorised as a Destructive tool in the AWS DynamoDB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS DynamoDB MCP Server MCP server in PolicyLayer and add a rule for policy_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 DynamoDB MCP Server. Nothing to install.
policy_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 policy_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 policy_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.
policy_delete is provided by the AWS DynamoDB MCP Server MCP server (awslabs.dynamodb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS DynamoDB 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 DynamoDB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.