AI agents call list_destinations to retrieve information from Zhook without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays configuration data about webhook destinations. It performs a query/list operation without creating, modifying, deleting, or executing any actions. The 'list' verb and read-only nature of retrieving existing configuration make this a Read category tool with low severity risk, as misuse would only expose metadata about destinations rather than cause data loss or unintended operations.
From the tool's definition Tool name 'list_destinations' and description 'List all destinations configured for a specific webhook' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all destinations configured for a specific webhook. It is categorised as a Read tool in the Zhook MCP Server, which means it retrieves data without modifying state.
Register the Zhook MCP server in PolicyLayer and add a rule for list_destinations: 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.
list_destinations is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_destinations 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.
Set action: deny in the PolicyLayer policy for list_destinations. 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.
list_destinations 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →