AI agents invoke benchmark_run to trigger actions in Ruflo. 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.
This tool triggers execution of performance benchmarks, which involves running code/operations that consume system resources and whose effects depend on how benchmarks are configured. This is Execute (not Read, as it actively triggers operations beyond querying).
From the tool's definition Tool description states 'Execute performance benchmarks' — the verb 'Execute' combined with 'benchmarks' indicates the tool runs computational operations whose side effects and resource consumption depend on benchmark parameters and system state.
Attacks that exploit this kind of access
Execute performance benchmarks (V2 compatible). Deprecated: Use system/metrics instead. It is categorised as a Execute tool in the Ruflo MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ruflo 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 Ruflo. Nothing to install.
benchmark_run 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 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.
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.
benchmark_run is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
benchmark_run is one line of Ruflo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →