claims_rebalance · Claude Flow MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why claims_rebalance needs a policy

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

Recommended rule Ready

Verdict

claims_rebalance Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "claims_rebalance": {
      "limits": [
        {
          "counter": "claims_rebalance_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 Claude Flow, so you can run agents against it safely.

FAQ

Questions about claims_rebalance

What does the claims_rebalance tool do? +

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.

How do I enforce a policy on claims_rebalance? +

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.

What risk level is claims_rebalance? +

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

Can I rate-limit claims_rebalance? +

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.

How do I block claims_rebalance completely? +

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.

What MCP server provides claims_rebalance? +

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.