AI agents call hooks_list to retrieve information from Ruflo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/list operation that retrieves information about registered hooks in the system. It has no side effects, does not modify data, and does not execute code or trigger external operations. The incomplete description ('Use when native Bash hooks (via Claude Code\') does not suggest any capabilities beyond listing, which lowers confidence slightly but does not change the category.
From the tool's definition Tool name 'hooks_list' and description indicate it 'List[s] all registered hooks' — a read-only operation that retrieves and displays hook metadata without modifying or executing anything.
Attacks that exploit this kind of access
List all registered hooks Use when native Bash hooks (via Claude Code\. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo 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 Ruflo. Nothing to install.
hooks_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
hooks_list is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
hooks_list is one line of Ruflo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →