claims_release

Release a gateway-held work claim. Authorised by OAuth swarm:publish or the service-side admin token.

SERVERClaude Flow SOURCEclaude-flow

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/claims-release.md

WHAT IT DOES

What claims_release does on Claude Flow

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

RISK

Why claims_release is rated Medium

Releases a held claim, modifying workflow state reversibly without destructive or financial effects.

From the tool's definition Release a gateway-held work claim

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

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

claims_release Rate-limited

claims_release 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_release": {
      "limits": [
        {
          "counter": "claims_release_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about claims_release

What does the claims_release tool do? +

Release a gateway-held work claim. Authorised by OAuth swarm:publish or the service-side admin token. It is categorised as a Write tool in the Claude Flow 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_release? +

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

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

Can I rate-limit claims_release? +

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

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

claims_release 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 546 Claude Flow tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →