performance_benchmark
Run performance benchmarks Use when native shell timing (
This record as markdown: /tools/ruflo/performance-benchmark.md
What performance_benchmark does on Ruflo
AI agents invoke performance_benchmark 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.
Why performance_benchmark is rated High
This tool executes performance benchmarks, which constitutes running external operations whose effects depend on arguments. The incomplete description mentions 'native shell timing,' suggesting shell command execution. While benchmarks are typically read-only in intent, the ability to run shell commands classifies this as Execute rather than Read.
From the tool's definition Tool name 'performance_benchmark' combined with description 'Run performance benchmarks Use when native shell timing' indicates execution of benchmark operations, likely involving shell commands or external process invocation.
Attacks that exploit this kind of access
The rule that runs performance_benchmark safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For performance_benchmark, this is the rule to start with:
performance_benchmark 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every performance_benchmark call is checked against it from then on.
Questions about performance_benchmark
Run performance benchmarks Use when native shell timing (. 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 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 Ruflo. 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 Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
Across the catalogue