Medium Risk

updateWebhook

Update webhook configuration including URL, monitored addresses, or transaction type filters. Use this to add/remove addresses or change which transaction types trigger notifications. Credit cost: 100 credits/call (management operation).

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

helius-mcp Write

AI agents use updateWebhook to create or modify resources in Helius. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call updateWebhook repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Helius.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

helius.yaml
tools:
  updateWebhook:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Helius policy for all 63 tools.

Tool Name updateWebhook
Category Write
MCP Server Helius MCP Server
Risk Level Medium

View all 63 tools →

Agents calling write-class tools like updateWebhook 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 Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the updateWebhook tool do? +

Update webhook configuration including URL, monitored addresses, or transaction type filters. Use this to add/remove addresses or change which transaction types trigger notifications. Credit cost: 100 credits/call (management operation).. It is categorised as a Write tool in the Helius MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on updateWebhook? +

Add a rule in your Intercept YAML policy under the tools section for updateWebhook. 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 updateWebhook? +

updateWebhook is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit updateWebhook? +

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

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

updateWebhook 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.