Critical Risk →

pylon_delete_webhook

Delete an existing webhook to stop sending notifications to an external system. Use this when removing integrations or cleaning up unused webhooks.

Part of the Pylon Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

marcinwyszynski/pylon-mcp Destructive Risk 4/5

AI agents may call pylon_delete_webhook to permanently remove or destroy resources in Pylon Server. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call pylon_delete_webhook in a loop, permanently destroying resources in Pylon Server. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

marcinwyszynski-pylon-mcp.yaml
tools:
  pylon_delete_webhook:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Pylon Server policy for all 29 tools.

Tool Name pylon_delete_webhook
Category Destructive
Risk Level Critical

View all 29 tools →

Agents calling destructive-class tools like pylon_delete_webhook have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

pylon_delete_webhook is one of the critical-risk operations in Pylon Server. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the pylon_delete_webhook tool do? +

Delete an existing webhook to stop sending notifications to an external system. Use this when removing integrations or cleaning up unused webhooks.. It is categorised as a Destructive tool in the Pylon 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 pylon_delete_webhook? +

Add a rule in your Intercept YAML policy under the tools section for pylon_delete_webhook. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Pylon Server MCP server.

What risk level is pylon_delete_webhook? +

pylon_delete_webhook 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 pylon_delete_webhook? +

Yes. Add a rate_limit block to the pylon_delete_webhook rule in your Intercept 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 pylon_delete_webhook completely? +

Set action: deny in the Intercept policy for pylon_delete_webhook. 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 pylon_delete_webhook? +

pylon_delete_webhook is provided by the Pylon Server MCP server (marcinwyszynski/pylon-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Pylon Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.