// SCAN REPORT

Zhook

18 tools. 9 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 3 Jul 2026

9 can modify or destroy data

9 read-only

18 tools total

Community server · catalogue entry verified 03/07/2026

How to control Zhook ↓

TOOL MAP

What Zhook exposes to your agents

Read (9) Write / Execute (7) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Zhook tools

Destructive · High delete_destination This tool irreversibly deletes a destination configuration from the webhook/hook system. Destructive · High delete_transformation The tool performs an irreversible deletion operation on a transformation resource. Execute · Medium trigger_webhook This tool executes an outbound action (sending a webhook/HTTP request) to an external service. Execute · Medium wait_for_event This tool initiates an active WebSocket connection and waits for an external event, triggering an external operation (network connection, blocking wait) whose outcome depends on runtime arguments.

9 of Zhook's 18 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Zhook

PolicyLayer is an MCP gateway — it sits between your AI agents and Zhook, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_destination": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_destination": {
    "limits": [
      {
        "counter": "create_destination_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_aggregated_hook_metrics": {
    "limits": [
      {
        "counter": "get_aggregated_hook_metrics_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Zhook — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ZHOOK →

Instant setup, no code required.

FULL CATALOGUE

All 18 Zhook tools

DESTRUCTIVE 2 tools

Destructive delete_destination Remove a destination from a hook. Destructive delete_transformation Delete a transformation from a hook.

EXECUTE 2 tools

Execute trigger_webhook Send a test webhook event to a specific Hook. This mimics a real third-party service sending data to the hook Execute wait_for_event Connects to the Zhook WebSocket and waits for the NEXT event to arrive on a specific hook. Returns the full ev

WRITE 5 tools

Write create_destination Add a new destination to a hook to forward events to. Write create_hook Create a new webhook or MQTT hook. Returns the new hook ID and its public URL. Write create_transformation Create a new JSONata transformation for a hook. Write update_destination Update an existing destination Write update_transformation Update an existing transformation.

READ 9 tools

Read get_aggregated_hook_metrics Get historical aggregated metrics for a specific hook with custom date ranges. Read get_destination Get detailed configuration for a specific destination. Read get_event Get the full JSON payload and details of a specific event. Read get_hook Get detailed configuration for a specific webhook, including delivery URL, metadata, and recent metrics. Read get_hook_metrics Get real-time metrics for a specific hook (request counts, success/failure rates). Read list_destinations List all destinations configured for a specific webhook. Read list_events List recent events received by a specific hook. Useful for checking what payloads have been delivered. Read list_hooks List all webhooks configured in the Zhook account. Returns hook IDs, URLs, and active status. Read list_transformations List all transformations configured for a specific webhook.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Zhook

Can an AI agent delete data through the Zhook MCP server? +

Yes. The Zhook server exposes 2 destructive tools including delete_destination, delete_transformation. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Zhook? +

The Zhook server has 5 write tools including create_destination, create_hook, create_transformation. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Zhook.

How many tools does the Zhook MCP server expose? +

18 tools across 4 categories: Destructive, Execute, Read, Write. 9 are read-only. 9 can modify, create, or delete data.

How do I enforce a policy on Zhook? +

Register the Zhook MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Zhook tool call.

Deterministic rules across all 18 Zhook tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ZHOOK →

Instant setup, no code required.

18 Zhook tools catalogued and risk-classified — across an index of 43,000+ MCP servers.