hook_create
Create a WEBHOOK TRIGGER for a SAVED rig: returns a secret hook URL; any outside system POSTing that URL fires the rig immediately (no polling), with the POST body threaded in as the rig's run input. Every fire draws on the owner's daily run budget (fail-closed); each hook is rate-limited to 6 fi...
This record as markdown: /tools/ai-rokha-rokha/hook-create.md
What hook_create does on Rokha
AI agents use hook_create to create or update resources in Rokha, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rokha environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
rig_id | string | Yes | UUID of the SAVED rig this webhook fires. |
rig_name | string | — | Optional display name for the hook. |
Parameters from the server's own tool schema.
Why hook_create is rated Medium
Creates a persistent webhook that lets anyone trigger rig execution, consuming run budget.
From the tool's definition Create a WEBHOOK TRIGGER...returns a secret hook URL; anyone holding it can fire
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs hook_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hook_create, this is the rule to start with:
hook_create stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every hook_create call is checked against it from then on.
Questions about hook_create
Create a WEBHOOK TRIGGER for a SAVED rig: returns a secret hook URL; any outside system POSTing that URL fires the rig immediately (no polling), with the POST body threaded in as the rig's run input. Every fire draws on the owner's daily run budget (fail-closed); each hook is rate-limited to 6 fires/minute. The URL is a SECRET — anyone holding it can fire the rig; delete the hook to revoke it. Requires a logged-in identity (Authorization: Bearer <JWT>). Cap: 10 hooks per account. It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
hook_create accepts 2 parameters: rig_id, rig_name. Required: rig_id. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for hook_create: 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 Rokha. Nothing to install.
hook_create 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 hook_create 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 hook_create. 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.
hook_create is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue