hooks_list

List all registered hooks Use when native Bash hooks (via Claude Code\

SERVERClaude Flow SOURCEclaude-flow

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/io-github-ruvnet-claude-flow/hooks-list.md

WHAT IT DOES

What hooks_list does on Claude Flow

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

RISK

Why hooks_list is rated Low

This tool retrieves and displays existing hook registrations without modifying, executing, or deleting anything. It is a purely informational query operation. The blast radius of misuse is minimal—an agent could only learn what hooks exist in the system, which is non-destructive read access.

From the tool's definition The tool name is 'hooks_list' and the description states 'List all registered hooks'. The verb 'List' and the action of retrieving/querying hook metadata indicates data retrieval with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hooks_list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hooks_list, this is the rule to start with:

hooks_list Allowed

hooks_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": {
    "hooks_list": {}
  }
}

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

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

FAQ

Questions about hooks_list

What does the hooks_list tool do? +

List all registered hooks Use when native Bash hooks (via Claude Code\. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hooks_list? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_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 Claude Flow. Nothing to install.

What risk level is hooks_list? +

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

Can I rate-limit hooks_list? +

Yes. Add a rate_limit block to the hooks_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 hooks_list completely? +

Set action: deny in the PolicyLayer policy for hooks_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 hooks_list? +

hooks_list is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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