delete_request

THE RISK

Critical Risk

Why delete_request needs a policy

This tool irreversibly removes stored request data from a webhook endpoint. Once deleted, the request record cannot be recovered. While the blast radius is limited to test/monitoring data rather than production systems, the irreversible nature of deletion places it in the Destructive category.

From the tool's definition Tool name is 'delete_request' with description stating it will 'Delete a specific request from a webhook.' The verb 'delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_request gives an agent:

POLICY

How to control delete_request

PolicyLayer is an MCP gateway — it sits between your AI agents and Webhook Site MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_request:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_request"
  ]
}

delete_request disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Webhook Site MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Webhook Site MCP Server tools

Destructive delete_all_requests Delete all requests from a webhook, optionally filtered by date range or query. Destructive delete_webhook Delete a webhook.site endpoint and all its data. Execute generate_ssrf_payload Generate SSRF (Server-Side Request Forgery) test payloads for bug bounty testing. Creates Execute generate_xss_callback Generate XSS (Cross-Site Scripting) callback payloads for bug bounty testing. Creates Java Execute send_multiple_requests Send multiple requests to a webhook in batch. Useful for load testing or sending multiple Execute send_to_webhook Send a POST request with JSON data to a webhook.site endpoint. Write create_webhook Create a new webhook.site endpoint. Returns the unique token/URL for the webhook. Write create_webhook_with_config Create a new webhook.site endpoint with custom configuration (response content, status, ti

All 23 Webhook Site MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Webhook Site MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_request

What does the delete_request tool do? +

Delete a specific request from a webhook. It is categorised as a Destructive tool in the Webhook Site 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_request? +

Register the Webhook Site MCP Server MCP server in PolicyLayer and add a rule for delete_request: 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 Webhook Site MCP Server. Nothing to install.

What risk level is delete_request? +

delete_request 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_request? +

Yes. Add a rate_limit block to the delete_request 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_request completely? +

Set action: deny in the PolicyLayer policy for delete_request. 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_request? +

delete_request is provided by the Webhook Site MCP Server MCP server (zebbern/webhook-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 Webhook Site MCP Server tool call.

Start from Webhook Site MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →