AI agents use create_webhook_inbox to create or update resources in Hookray — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hookray environment.
This tool creates a new data structure (webhook inbox) that is reversible — inboxes can be deleted or abandoned. It does not execute arbitrary code, delete data, or move money.
From the tool's definition Tool description states 'Create a new HookRay webhook inbox', which is a create operation that generates a new resource (public capture URL). The webhook inbox is a persistent artifact that will accept and store incoming HTTP requests.
Attacks that exploit this kind of access
Create a new HookRay webhook inbox and return its public capture URL. It is categorised as a Write tool in the Hookray MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hookray MCP server in PolicyLayer and add a rule for create_webhook_inbox: 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.
create_webhook_inbox is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_webhook_inbox 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 create_webhook_inbox. 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.
create_webhook_inbox 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 →