performance_metrics

Get detailed performance metrics Use when native shell timing (

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

WHAT IT DOES

What performance_metrics does on Claude Flow

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

The tool is described as getting/reading performance metrics, which is a read-only operation. The description appears truncated after 'native shell timing (' which slightly reduces confidence, but the core action is clearly data retrieval. Misuse potential is low as it only reads metrics.

From the tool's definition 'Get detailed performance metrics' — retrieves/queries performance data; no side effects indicated

Attacks that exploit this kind of access

RECOMMENDED RULE

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

performance_metrics Allowed

performance_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": {
    "performance_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 performance_metrics call is checked against it from then on.

FAQ

Questions about performance_metrics

What does the performance_metrics tool do? +

Get detailed performance metrics Use when native shell timing (. 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 performance_metrics? +

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

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

Can I rate-limit performance_metrics? +

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

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

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