hook_delete
Delete one of your webhook triggers by its hook id (from hook_list). This REVOKES the secret URL — outside systems still posting it get 404. The rig itself is untouched. Requires a logged-in identity.
This record as markdown: /tools/ai-rokha-rokha/hook-delete.md
What hook_delete does on Rokha
AI agents call hook_delete to permanently remove resources in Rokha, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
hook_id | string | Yes | UUID of the webhook trigger to delete. |
Parameters from the server's own tool schema.
Why hook_delete is rated Critical
Irreversibly deletes webhook configurations and revokes their secret URLs, preventing external integrations from functioning.
From the tool's definition Delete webhook triggers, REVOKES secret URL, outside systems get 404.
Attacks that exploit this kind of access
The rule that runs hook_delete 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_delete, this is the rule to start with:
hook_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every hook_delete call is checked against it from then on.
Questions about hook_delete
Delete one of your webhook triggers by its hook id (from hook_list). This REVOKES the secret URL — outside systems still posting it get 404. The rig itself is untouched. Requires a logged-in identity. It is categorised as a Destructive tool in the Rokha MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
hook_delete accepts 1 parameter: hook_id. Required: hook_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_delete: 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_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the hook_delete 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_delete. 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_delete 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.
Across the catalogue