update_destination · Zhook MCP: Risk & Policy

WHAT IT DOES

What update_destination does on Zhook

AI agents use update_destination to create or update resources in Zhook — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zhook environment.

WHY IT NEEDS A POLICY

Why update_destination needs a policy

This tool modifies existing configuration data (destinations) reversibly. While not destructive (the change can be undone by updating again), it affects the routing and delivery of webhooks/events, which could redirect sensitive data or disrupt integrations if misused by an agent. Classified as Write rather than Execute because it updates configuration objects, not triggering external operations.

From the tool's definition Tool name 'update_destination' and description 'Update an existing destination' indicate modification of existing data. The server context shows this is part of a webhook/MQTT hooks management system where destinations are delivery targets for events.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_destination Rate-limited

update_destination stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_destination": {
      "limits": [
        {
          "counter": "update_destination_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Zhook, so you can run agents against it safely.

FAQ

Questions about update_destination

What does the update_destination tool do? +

Update an existing destination. It is categorised as a Write tool in the Zhook MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_destination? +

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

What risk level is update_destination? +

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

Can I rate-limit update_destination? +

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

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

update_destination is provided by the Zhook MCP server (zhookteam/zhook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.