hook_list

List your webhook triggers: the secret hook URL, bound rig, enabled state, fire count, and last fire verdict (ok | partial | error | skipped_budget). Requires a logged-in identity.

SERVERRokha SOURCEhttps://rokha.ai/mcp/jsonrpc

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-rokha-rokha/hook-list.md

WHAT IT DOES

What hook_list does on Rokha

AI agents call hook_list to retrieve information from Rokha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why hook_list is rated Low

Retrieves webhook configuration and metadata without modifying or executing; exposes sensitive URLs.

From the tool's definition List webhook triggers, secret hook URL, fire count, last verdict

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hook_list 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_list, this is the rule to start with:

hook_list Allowed

hook_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hook_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every hook_list call is checked against it from then on.

FAQ

Questions about hook_list

What does the hook_list tool do? +

List your webhook triggers: the secret hook URL, bound rig, enabled state, fire count, and last fire verdict (ok | partial | error | skipped_budget). Requires a logged-in identity. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hook_list? +

Register the Rokha MCP server in PolicyLayer and add a rule for hook_list: 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.

What risk level is hook_list? +

hook_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hook_list? +

Yes. Add a rate_limit block to the hook_list 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.

How do I block hook_list completely? +

Set action: deny in the PolicyLayer policy for hook_list. 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.

What MCP server provides hook_list? +

hook_list 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.

KEEP EXPLORING

More on Rokha, and thousands of servers like it.

This server

All 216 Rokha tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →