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.
This record as markdown: /tools/ruflo/claims-list.md
What claims_list does on Ruflo
AI agents call claims_list 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.
Why claims_list is rated Low
This tool retrieves or queries claim/permission data for filtering and inspection purposes only. It has no side effects, does not modify state, and is used as a gating check before other operations. The mention of pairing it with 'claims_grant' for privilege checks further confirms this is a read-only query tool.
From the tool's definition Tool name 'claims_list' and description states 'List all claims or filter by criteria' — retrieves capability gating information with no modification capability.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs claims_list 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_list, this is the rule to start with:
claims_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every claims_list call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo 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 Ruflo. Nothing to install.
claims_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
claims_list 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.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue