1ly_claim_fees

Claim Bags fee share for a token (Bags only).

SERVER1ly SOURCE@1ly/mcp-server

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-1lystore-mcp-server/1ly-claim-fees.md

WHAT IT DOES

What 1ly_claim_fees does on 1ly

AI agents use 1ly_claim_fees to commit financial operations through 1ly, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why 1ly_claim_fees is rated Critical

Claiming fee share is a financial operation that triggers transfer of funds (fee revenue) to the caller. It commits a financial action on-chain, moving accumulated fees, which falls squarely in the Financial category. Misuse could result in unauthorized claiming of fees or draining fee pools.

From the tool's definition 'Claim Bags fee share for a token' — this action moves/collects financial proceeds (fee share) associated with a token on the Bags.fm platform

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs 1ly_claim_fees safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 1ly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For 1ly_claim_fees, this is the rule to start with:

1ly_claim_fees Approval-gated

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

View as policy code

policy.json

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

GATE THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 1ly, apply this rule, and every 1ly_claim_fees call is checked against it from then on.

FAQ

Questions about 1ly_claim_fees

What does the 1ly_claim_fees tool do? +

Claim Bags fee share for a token (Bags only). It is categorised as a Financial tool in the 1ly MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on 1ly_claim_fees? +

Register the 1ly MCP server in PolicyLayer and add a rule for 1ly_claim_fees: 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 1ly. Nothing to install.

What risk level is 1ly_claim_fees? +

1ly_claim_fees 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 1ly_claim_fees? +

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

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

1ly_claim_fees is provided by the 1ly MCP server (@1ly/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 1ly, and thousands of servers like it.

This server

All 24 1ly tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →