claims_load

Get agent load information 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.

SERVERRuflo SOURCEruvnet/ruflo

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ruflo/claims-load.md

WHAT IT DOES

What claims_load does on Ruflo

AI agents call claims_load to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why claims_load is rated Low

This tool reads agent load/resource metrics and claims state without modifying or executing anything. It is purely informational, used to check conditions before privileged operations rather than performing those operations themselves. The blast radius of misuse is low — an agent retrieving load information cannot directly harm systems or data.

From the tool's definition claims_load is described as 'Get agent load information' — a retrieval operation with no side effects. The description indicates it retrieves per-agent capability and resource state to inform downstream access-control decisions.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs claims_load safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claims_load, this is the rule to start with:

claims_load Allowed

claims_load is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "claims_load": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every claims_load call is checked against it from then on.

FAQ

Questions about claims_load

What does the claims_load tool do? +

How do I enforce a policy on claims_load? +

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

claims_load is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit claims_load? +

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

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

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

KEEP EXPLORING

More on Ruflo, and thousands of servers like it.

This server

All 496 Ruflo tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →