RuVector intelligence system status (shows REAL metrics from memory store) Use when native Bash hooks (via Claude Code\
AI agents call hooks_intelligence to retrieve information from Claude Flow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays intelligence metrics and system status from an in-memory store. There is no indication it modifies data, executes commands, deletes anything, or moves money. The description is truncated ('Use when native Bash hooks (via Claude Code\'), but the evident purpose is diagnostic monitoring—a classic Read operation with low risk if misused by an AI agent.
From the tool's definition Tool name 'hooks_intelligence' and description 'status (shows REAL metrics from memory store)' indicate retrieval and monitoring of system state without modification. The phrase 'shows' and 'status' are read-only operations.
Attacks that exploit this kind of access
RuVector intelligence system status (shows REAL metrics from memory store) 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.
Register the Claude Flow MCP server in PolicyLayer and add a rule for hooks_intelligence: 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.
hooks_intelligence 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_intelligence 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_intelligence. 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_intelligence 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.