Delete a webhook bin (soft delete)
AI agents call delete_bin to permanently remove resources in RequestBin MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although marked 'soft delete' (suggesting potential recovery), the user-facing operation is deletion of a webhook bin, which destroys the configured endpoint and its interaction history from the user's perspective. This is irreversible from a workflow standpoint and qualifies as Destructive.
From the tool's definition Tool name 'delete_bin' and description 'Delete a webhook bin (soft delete)' — the verb 'Delete' indicates irreversible removal of data (the bin and its associated request history/state).
Attacks that exploit this kind of access
Delete a webhook bin (soft delete). It is categorised as a Destructive tool in the RequestBin MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the RequestBin MCP Server MCP server in PolicyLayer and add a rule for delete_bin: 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 RequestBin MCP Server. Nothing to install.
delete_bin 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 delete_bin 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 delete_bin. 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.
delete_bin is provided by the RequestBin MCP Server MCP server (requestbin/mcp-server). 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 →