AI agents call get_destination 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 existing destination configuration data. It has no side effects, cannot modify data, and does not execute operations or trigger external actions. It is a straightforward read operation, presenting minimal risk unless the configuration itself contains highly sensitive credentials, which would warrant a medium rating in some contexts.
From the tool's definition Tool name 'get_destination' and description 'Get detailed configuration for a specific destination' indicate a retrieval operation that returns configuration details without modifying or executing anything.
Attacks that exploit this kind of access
Get detailed configuration for a specific destination. 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 get_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.
get_destination 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 get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
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 →