teammate_find_optimal_path
Find optimal message routing path between two teammates using BMSSP graph algorithms.
This record as markdown: /tools/io-github-ruvnet-claude-flow/teammate-find-optimal-path.md
What teammate_find_optimal_path does on Claude Flow
AI agents call teammate_find_optimal_path to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why teammate_find_optimal_path is rated Low
This tool retrieves and computes routing paths between teammates in what appears to be an internal message routing system. It performs a query/search operation on graph data to return an optimal path—a computation with no side effects, data modification, or external execution. The operation is purely informational and reverses readily if the result is not used. This is characteristic of a Read category tool.
From the tool's definition Tool name and description indicate a read-only operation: 'Find optimal message routing path' queries graph algorithms to return routing information.
Attacks that exploit this kind of access
The rule that runs teammate_find_optimal_path 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 teammate_find_optimal_path, this is the rule to start with:
teammate_find_optimal_path 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 Claude Flow, apply this rule, and every teammate_find_optimal_path call is checked against it from then on.
Questions about teammate_find_optimal_path
Find optimal message routing path between two teammates using BMSSP graph algorithms. 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 teammate_find_optimal_path: 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.
teammate_find_optimal_path 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 teammate_find_optimal_path 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 teammate_find_optimal_path. 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.
teammate_find_optimal_path 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.
This server
Across the catalogue