Get model routing statistics Use when native Bash hooks (via Claude Code\
AI agents call hooks_model-stats 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 metrics about model routing behavior. There is no indication it modifies state, executes arbitrary code, deletes data, or moves money. The incomplete description ('Use when native Bash hooks (via Claude Code\') appears truncated but does not suggest mutation or execution capabilities. This is a straightforward Read operation with minimal risk.
From the tool's definition Tool name and description indicate retrieval of statistics: 'Get model routing statistics'. The verb 'Get' and focus on statistics (observational data) indicate a read-only operation with no side effects.
Attacks that exploit this kind of access
Get model routing statistics 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_model-stats: 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_model-stats 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_model-stats 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_model-stats. 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_model-stats 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.