claims_load

SERVERClaude Flow SOURCEclaude-flow

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/io-github-ruvnet-claude-flow/claims-load.md

WHAT IT DOES

What claims_load does on Claude Flow

AI agents call claims_load to retrieve information from Claude Flow 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 queries agent load status to inform access-control decisions. It has no side effects—it does not grant, modify, or terminate privileges (those are distinct tools: claims_grant, agent_terminate). The severity is low because unauthorized reads of load metrics pose minimal risk compared to execution or destructive operations.

From the tool's definition "Get agent load information" — the tool retrieves load data. Description emphasizes use in capability gating and checking (read operations) rather than modification: "Pair claims_grant + claims_check before letting an agent run privileged ops." The word…

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 Claude Flow, 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 Claude Flow, 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? +

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. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on claims_load? +

Register the Claude Flow 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 Claude Flow. 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 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.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

The MCP Attack Database →

Guides

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