claims_handoff · Ruflo MCP: Risk & Policy

WHAT IT DOES

What claims_handoff does on Ruflo

AI agents invoke claims_handoff to trigger actions in Ruflo. 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_handoff needs a policy

This tool triggers a transfer of control and execution capability from one agent to another, potentially elevating privileges or enabling operations the original agent cannot perform. While not destructive by itself, it orchestrates the execution of privileged operations by other agents based on capability gating decisions.

From the tool's definition Tool description explicitly states it 'Request[s] handoff of an issue to another claimant' and references capability gating, permission checks ('claims_grant + claims_check'), and privileged operations.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

claims_handoff Rate-limited

claims_handoff 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_handoff": {
      "limits": [
        {
          "counter": "claims_handoff_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 Ruflo, so you can run agents against it safely.

FAQ

Questions about claims_handoff

What does the claims_handoff tool do? +

Request handoff of an issue to another claimant 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 Ruflo 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_handoff? +

Register the Ruflo MCP server in PolicyLayer and add a rule for claims_handoff: 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 Ruflo. Nothing to install.

What risk level is claims_handoff? +

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

Can I rate-limit claims_handoff? +

Yes. Add a rate_limit block to the claims_handoff 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_handoff completely? +

Set action: deny in the PolicyLayer policy for claims_handoff. 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_handoff? +

claims_handoff is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.