AI agents call wait_for_request to retrieve information from Hookray without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only waits and retrieves/monitors incoming data without modifying, deleting, or executing anything. It is a passive read/observe operation that blocks until a webhook arrives, then returns the captured request data.
From the tool's definition Block until a new webhook arrives at an inbox, or return a timeout result
Attacks that exploit this kind of access
Block until a new webhook arrives at an inbox, or return a timeout result. It is categorised as a Read tool in the Hookray MCP Server, which means it retrieves data without modifying state.
Register the Hookray MCP server in PolicyLayer and add a rule for wait_for_request: 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 Hookray. Nothing to install.
wait_for_request 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 wait_for_request 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 wait_for_request. 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.
wait_for_request is provided by the Hookray MCP server (shotatanikawa/hookray-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 →