ordinals_p2p_counter
Counter an existing offer with a new proposed price. Submits a counter-offer linked to a parent trade. The active wallet signs the counter with BIP-137 to prove identity. Either party in a trade may counter. Requires an unlocked wallet with Bitcoin keys.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/ordinals-p2p-counter.md
What ordinals_p2p_counter does on Aibtc
AI agents use ordinals_p2p_counter to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why ordinals_p2p_counter is rated Critical
This tool submits a financial counter-offer in a peer-to-peer Bitcoin/Ordinals trade, committing the user to a new proposed price and using cryptographic signing to bind their identity to the offer. This constitutes a financial obligation/commitment in a trading context.
From the tool's definition Counter an existing offer with a new proposed price. Submits a counter-offer linked to a parent trade. The active wallet signs the counter with BIP-137 to prove identity. Requires an unlocked wallet with Bitcoin keys.
Attacks that exploit this kind of access
The rule that runs ordinals_p2p_counter 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_counter, this is the rule to start with:
Any call to ordinals_p2p_counter is blocked until a human approves 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_counter call is checked against it from then on.
Questions about ordinals_p2p_counter
Counter an existing offer with a new proposed price. Submits a counter-offer linked to a parent trade. The active wallet signs the counter with BIP-137 to prove identity. Either party in a trade may counter. Requires an unlocked wallet with Bitcoin keys. 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.
Register the Aibtc MCP server in PolicyLayer and add a rule for ordinals_p2p_counter: 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_counter is a Financial 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_counter 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_counter. 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_counter 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