hooks_intelligence

RuVector intelligence system status (shows REAL metrics from memory store) 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-intelligence.md

WHAT IT DOES

What hooks_intelligence does on Claude Flow

AI agents call hooks_intelligence 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_intelligence is rated Low

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

RECOMMENDED RULE

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

hooks_intelligence Allowed

hooks_intelligence 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_intelligence": {}
  }
}

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_intelligence call is checked against it from then on.

FAQ

Questions about hooks_intelligence

What does the hooks_intelligence tool do? +

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.

How do I enforce a policy on hooks_intelligence? +

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.

What risk level is hooks_intelligence? +

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

Can I rate-limit hooks_intelligence? +

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.

How do I block hooks_intelligence completely? +

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.

What MCP server provides hooks_intelligence? +

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.

KEEP EXPLORING

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

This server

All 496 Claude Flow tools →

Across the catalogue

The MCP Attack Database →

Guides

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