Critical Risk →

claim_all_revenue

claim_all_revenue

How to control claim_all_revenue ↓

What claim_all_revenue does on Story SDK MCP Server

AI agents use claim_all_revenue to commit financial operations through Story SDK MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.

Critical Risk

Why claim_all_revenue needs a policy

The tool name 'claim_all_revenue' strongly implies a financial operation that moves or collects accumulated revenue/funds. In the context of a Story Protocol SDK server dealing with IP licensing, revenue sharing, and token operations, claiming revenue involves transferring financial value on-chain. This is a Financial category operation.

From the tool's definition Tool name 'claim_all_revenue' on a server that handles 'minting tokens', 'registering IP', and financial operations like 'deposit_wip' and 'get_license_minting_fee'

Documented attack patterns abuse exactly the kind of access claim_all_revenue gives an agent:

How to control claim_all_revenue

PolicyLayer is an MCP gateway — it sits between your AI agents and Story SDK MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for claim_all_revenue:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "claim_all_revenue": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

Any call to claim_all_revenue is blocked until a human approves it. The rest of the server keeps working.

  1. Create a free account and register Story SDK MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
GATE THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about claim_all_revenue

What does the claim_all_revenue tool do? +

claim_all_revenue. It is categorised as a Financial tool in the Story SDK MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on claim_all_revenue? +

Register the Story SDK MCP Server MCP server in PolicyLayer and add a rule for claim_all_revenue: 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 Story SDK MCP Server. Nothing to install.

What risk level is claim_all_revenue? +

claim_all_revenue is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit claim_all_revenue? +

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

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

claim_all_revenue is provided by the Story SDK MCP Server MCP server (piplabs/story-mcp-hub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Story SDK MCP Server tool call.

Start from Story SDK MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

25 Story SDK MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.