agenticow_status
agenticow — health/geometry of an .rvf memory file: {totalVectors, totalSegments, fileSize, currentEpoch, deadSpaceRatio, readOnly, chainDepth, dimension, metric}. Use when you need to check vector count before/after ingest, spot compaction pressure (deadSpaceRatio), or confirm the dimension befo...
This record as markdown: /tools/io-github-ruvnet-claude-flow/agenticow-status.md
What agenticow_status does on Claude Flow
AI agents call agenticow_status 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.
Why agenticow_status is rated Low
This tool retrieves metadata and status information about a vector memory file with no side effects. It performs diagnostics and validation (checking vector count, compaction pressure, dimensions) without creating, modifying, or deleting any data. The explicit 'Pure read' designation confirms classification as Read.
From the tool's definition Tool description explicitly states 'Pure read' and lists only informational outputs: totalVectors, totalSegments, fileSize, currentEpoch, deadSpaceRatio, readOnly, chainDepth, dimension, metric. Use case is checking/confirming status, not modifying data.
Attacks that exploit this kind of access
The rule that runs agenticow_status 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 agenticow_status, this is the rule to start with:
agenticow_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every agenticow_status call is checked against it from then on.
Questions about agenticow_status
agenticow — health/geometry of an .rvf memory file: {totalVectors, totalSegments, fileSize, currentEpoch, deadSpaceRatio, readOnly, chainDepth, dimension, metric}. Use when you need to check vector count before/after ingest, spot compaction pressure (deadSpaceRatio), or confirm the dimension before ingesting into a shared base. Pure read. 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 agenticow_status: 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.
agenticow_status 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 agenticow_status 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 agenticow_status. 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.
agenticow_status 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.
More on Claude Flow, and thousands of servers like it.
This server
Across the catalogue