mcp_status
Get MCP server status, including stdio mode detection Use when native Claude Code MCP status is wrong because you need Ruflo-side server detail — tool counts per namespace, transport stats, MCP handshake errors. For just
This record as markdown: /tools/io-github-ruvnet-claude-flow/mcp-status.md
What mcp_status does on Claude Flow
AI agents call mcp_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 mcp_status is rated Low
This tool retrieves diagnostic and status information about MCP server state without performing any mutations, triggering external operations, or side effects. It is a pure information-gathering tool for troubleshooting and monitoring purposes, fitting the Read category. Blast radius is minimal since status queries cannot damage systems.
From the tool's definition Tool name is 'mcp_status' and description states 'Get MCP server status' with read-only intent: 'tool counts per namespace, transport stats, MCP handshake errors.' The verb 'Get' and focus on monitoring/observability indicate data retrieval with no…
Attacks that exploit this kind of access
The rule that runs mcp_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 mcp_status, this is the rule to start with:
mcp_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 mcp_status call is checked against it from then on.
Questions about mcp_status
Get MCP server status, including stdio mode detection Use when native Claude Code MCP status is wrong because you need Ruflo-side server detail — tool counts per namespace, transport stats, MCP handshake errors. For just. 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 mcp_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.
mcp_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 mcp_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 mcp_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.
mcp_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