ordinals_p2p_cancel
Cancel an open offer or counter on the trade ledger. Only the parties involved in a trade may cancel it. The active wallet signs the cancellation with BIP-137 to prove authorization. Requires an unlocked wallet with Bitcoin keys.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/ordinals-p2p-cancel.md
What ordinals_p2p_cancel does on Aibtc
AI agents call ordinals_p2p_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.
Why ordinals_p2p_cancel is rated Critical
This tool irreversibly removes/cancels active trade offers from a ledger. While only authorized parties (wallet owners) can invoke it, the action itself destroys a trade state that cannot be recovered. This qualifies as Destructive rather than Execute because the primary effect is permanent removal of data/state.
From the tool's definition 'Cancel an open offer or counter on the trade ledger' and 'The active wallet signs the cancellation with BIP-137' indicate irreversible deletion of an open trade position. The tool removes an existing offer from the ledger that cannot be undone.
Attacks that exploit this kind of access
The rule that runs ordinals_p2p_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 ordinals_p2p_cancel, this is the rule to start with:
ordinals_p2p_cancel is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every ordinals_p2p_cancel call is checked against it from then on.
Questions about ordinals_p2p_cancel
Cancel an open offer or counter on the trade ledger. Only the parties involved in a trade may cancel it. The active wallet signs the cancellation with BIP-137 to prove authorization. Requires an unlocked wallet with Bitcoin keys. 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.
Register the Aibtc MCP server in PolicyLayer and add a rule for ordinals_p2p_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.
ordinals_p2p_cancel is a Destructive 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 ordinals_p2p_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.
Set action: deny in the PolicyLayer policy for ordinals_p2p_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.
ordinals_p2p_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.
More on Aibtc, and thousands of servers like it.
Across the catalogue