AI agents call list_events 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 historical event data from a webhook without side effects. It allows querying past events for monitoring or debugging purposes, but does not modify, execute, or delete anything. The blast radius of misuse is minimal — an agent could only view events that have already been received, which presents no destructive or operational risk.
From the tool's definition Tool name is 'list_events' and description states 'List recent events received by a specific hook' — a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
List recent events received by a specific hook. Useful for checking what payloads have been delivered. 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_events: 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_events 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_events 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_events. 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_events 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 →