Critical Risk →

deleteWebhook

Delete a webhook by its ID. This permanently removes the webhook and stops all notifications. Credit cost: 100 credits/call (management operation).

Single-target operation

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

helius-mcp Destructive

AI agents may call deleteWebhook to permanently remove or destroy resources in Helius. 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 deleteWebhook in a loop, permanently destroying resources in Helius. 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.

helius.yaml
tools:
  deleteWebhook:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Helius policy for all 63 tools.

Tool Name deleteWebhook
Category Destructive
MCP Server Helius MCP Server
Risk Level Critical

View all 63 tools →

Agents calling destructive-class tools like deleteWebhook 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.

deleteWebhook is one of the critical-risk operations in Helius. 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 deleteWebhook tool do? +

Delete a webhook by its ID. This permanently removes the webhook and stops all notifications. Credit cost: 100 credits/call (management operation).. It is categorised as a Destructive tool in the Helius 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 deleteWebhook? +

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

What risk level is deleteWebhook? +

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

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

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

deleteWebhook is provided by the Helius MCP server (helius-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.