claims_list

List all claims or filter by criteria 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.

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-list.md

WHAT IT DOES

What claims_list does on Claude Flow

AI agents call claims_list 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_list is rated Low

This is a query/retrieval operation that reads claim records to inspect agent capabilities and permissions. It has no side effects, does not execute operations, and does not modify data. The description explicitly frames it as a lookup mechanism paired with grant/check operations for access control, not as a standalone action.

From the tool's definition Tool name 'claims_list' and description states 'List all claims or filter by criteria' — retrieves capability/permission metadata without modification.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs claims_list 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_list, this is the rule to start with:

claims_list Allowed

claims_list 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_list": {}
  }
}

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_list call is checked against it from then on.

FAQ

Questions about claims_list

What does the claims_list tool do? +

How do I enforce a policy on claims_list? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for claims_list: 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_list? +

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

Can I rate-limit claims_list? +

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

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

claims_list 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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