claims_rebalance
Suggest or apply load rebalancing across agents Use when nothing native covers per-agent capability gating — Claude Code agents have file-system access by default. Pair claims_grant + claims_check before letting an agent run privileged ops. For trusted in-session work, no claims call is needed.
This record as markdown: /tools/io-github-ruvnet-claude-flow/claims-rebalance.md
What claims_rebalance does on Claude Flow
AI agents invoke claims_rebalance 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 claims_rebalance is rated High
This tool executes rebalancing operations across agent infrastructure and controls capability access. While not destructive (changes are reversible), it performs active operations that reconfigure agent pool behavior and can enable/restrict agent capabilities. This fits Execute rather than Write because it triggers external orchestration effects and controls access to privileged operations, making misuse high-impact.
From the tool's definition 'apply load rebalancing across agents' and 'capability gating' and 'privileged ops' indicate this tool triggers external operations that reconfigure agent behavior and access control.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs claims_rebalance 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 claims_rebalance, this is the rule to start with:
claims_rebalance 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 claims_rebalance call is checked against it from then on.
Questions about claims_rebalance
Suggest or apply load rebalancing across agents Use when nothing native covers per-agent capability gating — Claude Code agents have file-system access by default. Pair claims_grant + claims_check before letting an agent run privileged ops. For trusted in-session work, no claims call is needed. 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 claims_rebalance: 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.
claims_rebalance 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 claims_rebalance 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 claims_rebalance. 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.
claims_rebalance 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