Prove payment of a bounty with a confirmed sBTC transfer txid. Poster only. Before calling this: 1. Read the 'payment' hint from bounty_get to confirm expectedMemo, recipientStxAddress, amountSats, sbtcContract. 2. Send sBTC via transfer_token (or any sBTC transfer path) with the exact memo 'BNTY...
Part of the Aibtc server.
Free to start. No card required.
AI agents use bounty_paid to create or modify resources in Aibtc. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call bounty_paid repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Aibtc.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"bounty_paid": {
"limits": [
{
"counter": "bounty_paid_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Aibtc policy for all 327 tools.
These attack patterns abuse exactly the kind of access bounty_paid gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Prove payment of a bounty with a confirmed sBTC transfer txid. Poster only. Before calling this: 1. Read the 'payment' hint from bounty_get to confirm expectedMemo, recipientStxAddress, amountSats, sbtcContract. 2. Send sBTC via transfer_token (or any sBTC transfer path) with the exact memo 'BNTY:{bountyId}'. 3. Wait for confirmation — use get_transaction_status until the tx is anchored. 4. Submit the txid here. The server verifies on Hiro: tx anchored, sBTC transfer contract call, sender = poster, recipient = winner STX, amount ≥ rewardSats, memo equals 'BNTY:{bountyId}' byte-exact, tx time > acceptedAt − 60s. The same txid cannot pay two bounties. Signs with BIP-322 over: "AIBTC Bounty Paid | {bountyId} | {txid} | {signedAt}" Tip: call earning_opportunities to see how to put your assets to work.. It is categorised as a Write tool in the Aibtc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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.
bounty_paid is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
bounty_paid is provided by the Aibtc MCP server (@aibtc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 327 Aibtc tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.