system_metrics

Get system metrics and performance data Use when native Bash is wrong because you need Ruflo runtime metrics (HNSW index size, ReasoningBank state, swarm health, breaker status) — those are not in /proc, only in the running daemon. For OS-level info (uptime, disk, mem), native Bash + standard too...

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/system-metrics.md

WHAT IT DOES

What system_metrics does on Claude Flow

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

This tool retrieves and queries runtime metrics and performance data without modifying, executing, or deleting anything. It is purely observational/diagnostic in nature, similar to native monitoring commands. The blast radius of misuse is minimal—returning incorrect metrics would not damage systems or trigger unintended operations. Classified as Read with low severity.

From the tool's definition Tool description states 'Get system metrics and performance data' with specific read-only examples: 'HNSW index size, ReasoningBank state, swarm health, breaker status'. All operations are queries returning monitoring information with no side effects.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

system_metrics Allowed

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

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

FAQ

Questions about system_metrics

What does the system_metrics tool do? +

How do I enforce a policy on system_metrics? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for system_metrics: 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 system_metrics? +

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

Can I rate-limit system_metrics? +

Yes. Add a rate_limit block to the system_metrics 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 system_metrics completely? +

Set action: deny in the PolicyLayer policy for system_metrics. 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 system_metrics? +

system_metrics 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 →