Delete a DynamoDB table
AI agents call dynamodb_table_delete to permanently remove resources in AWS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a DynamoDB table permanently removes all data within it and the table itself—this cannot be undone without restoration from backups. This is the most severe category as it represents complete data loss at the table level. The blast radius is critical: an AI agent misdirected to call this tool could destroy production databases. This unambiguously falls under Destructive rather than Write, Execute, or Read.
From the tool's definition Tool name and description explicitly state 'Delete a DynamoDB table', which is an irreversible deletion of infrastructure/data storage.
Attacks that exploit this kind of access
Delete a DynamoDB table. It is categorised as a Destructive tool in the AWS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS MCP Server MCP server in PolicyLayer and add a rule for dynamodb_table_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 MCP Server. Nothing to install.
dynamodb_table_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 dynamodb_table_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 dynamodb_table_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.
dynamodb_table_delete is provided by the AWS MCP Server MCP server (rishikavikondala/mcp-server-aws). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →