Detect performance bottlenecks Use when native shell timing (
AI agents call performance_bottleneck to retrieve information from Claude Flow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to detect and report on performance bottlenecks, which is a read/diagnostic operation. The description is truncated ('Use when native shell timing ('), which reduces confidence. Based on the available text, it seems to analyze performance data rather than modify anything.
From the tool's definition 'Detect performance bottlenecks' — implies analysis/observation of system performance metrics
Attacks that exploit this kind of access
Detect performance bottlenecks Use when native shell timing (. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for performance_bottleneck: 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_bottleneck 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_bottleneck 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_bottleneck. 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_bottleneck 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.