This record as markdown: /tools/launch-on-basis-mcp-ts/claim-bounty.md
What claim_bounty does on Basis MCP Server
AI agents use claim_bounty to commit financial operations through Basis MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why claim_bounty is rated Critical
Claiming a bounty triggers a financial transaction where funds are transferred to the claimant. This is a financial operation as it moves value (bounty rewards) from the protocol to the user. Misuse or incorrect invocation could result in unintended financial claims or losses within the DeFi protocol context.
From the tool's definition 'Claim resolution bounty' — claiming a bounty involves receiving financial payment/reward from the protocol
Attacks that exploit this kind of access
The rule that runs claim_bounty safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claim_bounty, this is the rule to start with:
Any call to claim_bounty is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Basis MCP Server, apply this rule, and every claim_bounty call is checked against it from then on.
Questions about claim_bounty
Claim resolution bounty. It is categorised as a Financial tool in the Basis MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for claim_bounty: 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 Basis MCP Server. Nothing to install.
claim_bounty is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the claim_bounty 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 claim_bounty. 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.
claim_bounty is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Basis MCP Server, and thousands of servers like it.
Across the catalogue