bounty_paid

Prove payment of a bounty with a confirmed sBTC transfer txid. Poster only. Before calling this: 1. Read the

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/bounty-paid.md

WHAT IT DOES

What bounty_paid does on Aibtc

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

RISK

Why bounty_paid is rated Critical

This tool records or confirms a financial payment (bounty) involving sBTC (a Bitcoin-backed asset). It commits a financial obligation/transaction on-chain, making it Financial category. The 'Poster only' restriction indicates it triggers a financial settlement action. Severity is high due to irreversible on-chain financial transactions.

From the tool's definition Prove payment of a bounty with a confirmed sBTC transfer txid

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bounty_paid safely

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

bounty_paid Approval-gated

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

FAQ

Questions about bounty_paid

What does the bounty_paid tool do? +

Prove payment of a bounty with a confirmed sBTC transfer txid. Poster only. Before calling this: 1. Read the. It is categorised as a Financial tool in the Aibtc MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on bounty_paid? +

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

What risk level is bounty_paid? +

bounty_paid 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 bounty_paid? +

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

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

bounty_paid is provided by the Aibtc MCP server (aibtcdev/aibtc-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 Aibtc, and thousands of servers like it.

This server

All 358 Aibtc 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 →