AI agents call dropCollection to permanently remove resources in Amazon Data Processing MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The term 'drop' in database contexts universally means to delete/remove an entire collection and all its data. Despite the empty description, the function name itself is unambiguous and indicates permanent data loss. This represents the highest risk category (Destructive) with critical severity due to the irreversible nature and potential for catastrophic data loss if invoked incorrectly by an AI agent.
From the tool's definition Tool name 'dropCollection' explicitly indicates deletion of a database collection, which is an irreversible operation that cannot be undone.
Documented attack patterns abuse exactly the kind of access dropCollection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Data Processing MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for dropCollection:
{
"version": "1",
"default": "deny",
"hide": [
"dropCollection"
]
}dropCollection 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.
dropCollection. It is categorised as a Destructive tool in the Amazon Data Processing MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Amazon Data Processing MCP Server MCP server in PolicyLayer and add a rule for dropCollection: 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 Data Processing MCP Server. Nothing to install.
dropCollection 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 dropCollection 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 dropCollection. 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.
dropCollection is provided by the Amazon Data Processing MCP Server MCP server (awslabs.aws-dataprocessing-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Amazon Data Processing 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 Data Processing MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.