bounty_cancel

Cancel a bounty. Only the poster can call this, and only while status is

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity verified Pull the record →

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

WHAT IT DOES

What bounty_cancel does on Aibtc

AI agents call bounty_cancel to permanently remove resources in Aibtc, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why bounty_cancel is rated Critical

Cancelling a bounty is an irreversible action that permanently terminates it, making it Destructive. The restriction to the poster and status condition suggest a significant, non-undoable operation. Severity is high because it could destroy a financial commitment/agreement on-chain, though it falls short of 'Financial' since it cancels rather than moves money (though it may release funds).

From the tool's definition 'Cancel a bounty' — cancellation is an irreversible state change that terminates the bounty; 'Only the poster can call this' implies a privileged, final action

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bounty_cancel 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_cancel, this is the rule to start with:

bounty_cancel Hidden

bounty_cancel is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "bounty_cancel"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about bounty_cancel

What does the bounty_cancel tool do? +

Cancel a bounty. Only the poster can call this, and only while status is. It is categorised as a Destructive tool in the Aibtc MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on bounty_cancel? +

Register the Aibtc MCP server in PolicyLayer and add a rule for bounty_cancel: 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_cancel? +

bounty_cancel is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit bounty_cancel? +

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

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

bounty_cancel 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

sms_cancel_scheduled on Twilio SMS MCP Server →cancel_all_orders on Lighter MCP → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →