performance_profile · Ruflo MCP: Risk & Policy

WHAT IT DOES

What performance_profile does on Ruflo

AI agents invoke performance_profile 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 IT NEEDS A POLICY

Why performance_profile needs a policy

Profiling a component or operation requires actively running or instrumenting it, which constitutes execution. The mention of 'native shell timing' strongly suggests shell-level execution is involved. In a multi-agent swarm harness, misuse could trigger unintended operations across agents, warranting high severity. Confidence is slightly reduced because the description is truncated and full behavior is unclear.

From the tool's definition 'Profile specific component or operation' and reference to 'native shell timing' — implies execution of profiling operations against live components/operations in a multi-agent swarm environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

performance_profile Rate-limited

performance_profile 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": {
    "performance_profile": {
      "limits": [
        {
          "counter": "performance_profile_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ruflo, so you can run agents against it safely.

FAQ

Questions about performance_profile

What does the performance_profile tool do? +

Profile specific component or operation 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.

How do I enforce a policy on performance_profile? +

Register the Ruflo MCP server in PolicyLayer and add a rule for performance_profile: 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.

What risk level is performance_profile? +

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

Can I rate-limit performance_profile? +

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

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

performance_profile 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.