Run performance benchmarks Use when native shell timing (
AI agents invoke performance_benchmark 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.
The tool runs performance benchmarks, which implies executing code or shell commands whose effects depend on the arguments provided and system state. This is an Execute category tool rather than Read because it actively runs operations (benchmarking) rather than passively retrieving data.
From the tool's definition Tool name "performance_benchmark" combined with description "Run performance benchmarks Use when native shell timing" indicates execution of benchmarking operations, likely involving shell commands or code execution.
Attacks that exploit this kind of access
Run performance benchmarks Use when native shell timing (. 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.
Register the Claude Flow MCP server in PolicyLayer and add a rule for performance_benchmark: 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.
performance_benchmark is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the performance_benchmark 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 performance_benchmark. 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.
performance_benchmark 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.