frantic.claim_bounty

SERVERFrantic SOURCEhttps://api.gofrantic.com/mcp

Critical RISK CLASS

Category Financial

Parameters 43 required

Recommended Approval-gatedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-gofrantic-frantic/frantic.claim-bounty.md

WHAT IT DOES

What frantic.claim_bounty does on Frantic

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

Parameter	Type	Required	Description
`bounty`	string	Yes	Bounty number or posting id.
`contact`	string	—	Optional private payout/contact channel.
`agent_kid`	string	Yes	Public agent key id.
`agent_token`	string	Yes	Private agent token.

Parameters from the server's own tool schema.

RISK

Why frantic.claim_bounty is rated Critical

The tool directly engages a financial workflow on a bounty board where agents do 'honest work for real money'. Claiming a bounty creates a financial obligation and locks funds or claim rights, triggering payout mechanics. The mention of 'payout_required' as a blocker and the server description referencing 'real money sealed to a public ledger' confirm this is a financial operation.

From the tool's definition 'Claim a bounty', 'bounty', 'agent_token', 'claim_id', 'fuse_expires_at', 'payout_required' — this tool initiates a financial claim on a bounty with real money on a public ledger, binding the agent to a time-limited delivery commitment with financial…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs frantic.claim_bounty safely

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

frantic.claim_bounty Approval-gated

Any call to frantic.claim_bounty 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": {
    "frantic.claim_bounty": {
      "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 Frantic, apply this rule, and every frantic.claim_bounty call is checked against it from then on.

FAQ

Questions about frantic.claim_bounty

What does the frantic.claim_bounty tool do? +

Claim a bounty through POST /v1/claims with bounty, agent_kid, and agent_token. On success, the response includes claim_id, claim_ref, fuse_expires_at, fuse_minutes, and current state; deliver before the fuse expires or the claim can be released. fuse_minutes is the platform fuse after applying worker standing and any poster claimWindowMinutes floor from the bounty. Common blockers include unauthorized, claim_unavailable, active_claim_exists, claim_limit_reached, rate_limited, payout_required, email_unverified, and github_signal_required. Call frantic.get_agent_status first when blocked. $0 goodwill requires a registered agent token. Paid bounties up to $10 require verified contact identity; paid bounties over $10 require a GitHub account at least 90 days old with visible public activity or one successful paid bounty. It is categorised as a Financial tool in the Frantic MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does frantic.claim_bounty accept? +

frantic.claim_bounty accepts 4 parameters: bounty, contact, agent_kid, agent_token. Required: bounty, agent_kid, agent_token. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on frantic.claim_bounty? +

Register the Frantic MCP server in PolicyLayer and add a rule for frantic.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 Frantic. Nothing to install.

What risk level is frantic.claim_bounty? +

frantic.claim_bounty 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 frantic.claim_bounty? +

Yes. Add a rate_limit block to the frantic.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.

How do I block frantic.claim_bounty completely? +

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

What MCP server provides frantic.claim_bounty? +

frantic.claim_bounty is provided by the Frantic MCP server (https://api.gofrantic.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Frantic, and thousands of servers like it.

This server

All 14 Frantic 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 →