performance_report
Generate performance report Use when native shell timing (
This record as markdown: /tools/ruflo/performance-report.md
What performance_report does on Ruflo
AI agents call performance_report to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why performance_report is rated Low
The tool generates a performance report, which is a read/query operation that collects and presents metrics. However, the description is truncated ('Use when native shell timing ('), which lowers confidence. Given the context of a multi-agent swarm harness, this report likely reads from agent metrics and timing data without modifying state.
From the tool's definition 'Generate performance report' - the tool reads and aggregates performance metrics/timing data
Attacks that exploit this kind of access
The rule that runs performance_report 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_report, this is the rule to start with:
performance_report is read-only, so it stays allowed. 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_report call is checked against it from then on.
Questions about performance_report
Generate performance report Use when native shell timing (. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo MCP server in PolicyLayer and add a rule for performance_report: 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_report is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the performance_report 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_report. 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_report 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.
This server
Across the catalogue