performance_profile
Profile specific component or operation Use when native shell timing (
This record as markdown: /tools/io-github-ruvnet-claude-flow/performance-profile.md
What performance_profile does on Claude Flow
AI agents invoke performance_profile 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.
Why performance_profile is rated High
Profiling is an active operation that instruments and runs code to measure performance characteristics. While not destructive or dangerous by design, it executes external operations (profiling logic, shell-level timing/instrumentation) whose side effects depend on what component is targeted.
From the tool's definition Tool name 'performance_profile' and description 'Profile specific component or operation' with reference to 'native shell timing' indicate this tool executes profiling operations on system components, which involves running diagnostic code or commands whose…
Attacks that exploit this kind of access
The rule that runs performance_profile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For performance_profile, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every performance_profile call is checked against it from then on.
Questions about performance_profile
Profile specific component or operation 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_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 Claude Flow. Nothing to install.
performance_profile 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_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.
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.
performance_profile 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.
More on Claude Flow, and thousands of servers like it.
Across the catalogue