claims_claim · Ruflo MCP: Risk & Policy

WHAT IT DOES

What claims_claim does on Ruflo

AI agents use claims_claim to create or update resources in Ruflo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ruflo environment.

WHY IT NEEDS A POLICY

Why claims_claim needs a policy

The tool creates or modifies a claim record (assigning an issue to an agent or human), which is a reversible write operation. It does not execute code, delete data, or move money. However, it gates privileged operations for agents, so misuse could indirectly enable higher-severity actions, warranting medium severity.

From the tool's definition 'Claim an issue for work (human or agent)' and 'Pair claims_grant + claims_check before letting an agent run privileged ops' — the tool assigns/reserves an issue and modifies claim state

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

claims_claim Rate-limited

claims_claim stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_claim": {
      "limits": [
        {
          "counter": "claims_claim_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_claim

What does the claims_claim tool do? +

Claim an issue for work (human or agent) 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 Write tool in the Ruflo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on claims_claim? +

Register the Ruflo MCP server in PolicyLayer and add a rule for claims_claim: 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_claim? +

claims_claim is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit claims_claim? +

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

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

claims_claim 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.