benchmark_run

Execute performance benchmarks (V2 compatible). Deprecated: Use system/metrics instead.

SERVERClaude Flow SOURCEclaude-flow

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/benchmark-run.md

WHAT IT DOES

What benchmark_run does on Claude Flow

AI agents invoke benchmark_run to trigger actions in Claude Flow. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why benchmark_run is rated High

This tool runs performance benchmarks, which triggers external operations whose effects depend on arguments (what benchmark to run, parameters, etc.). Although benchmarking is typically non-destructive, it qualifies as Execute rather than Read because it actively runs code/operations that consume resources and produce side effects (CPU/memory usage, I/O, timing measurements).

From the tool's definition Tool name 'benchmark_run' combined with description 'Execute performance benchmarks' explicitly indicates execution of code or operations. The term 'Execute' is the core verb in the description.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

benchmark_run Rate-limited

benchmark_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "benchmark_run": {
      "limits": [
        {
          "counter": "benchmark_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every benchmark_run call is checked against it from then on.

FAQ

Questions about benchmark_run

What does the benchmark_run tool do? +

Execute performance benchmarks (V2 compatible). Deprecated: Use system/metrics instead. It is categorised as a Execute tool in the Claude Flow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on benchmark_run? +

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

benchmark_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit benchmark_run? +

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

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

benchmark_run 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 → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →