ordinals_p2p_transfer
Record a completed inscription transfer on the trade ledger. Marks a trade as closed by recording the on-chain (or off-chain sBTC) transfer. The active wallet signs the record with BIP-137 to prove the transfer was authorized by the sending party. Requires an unlocked wallet with Bitcoin keys.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/ordinals-p2p-transfer.md
What ordinals_p2p_transfer does on Aibtc
AI agents use ordinals_p2p_transfer to create or update resources in Aibtc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aibtc environment.
Why ordinals_p2p_transfer is rated Medium
This tool records/finalizes an inscription (NFT/ordinal) transfer on a trade ledger and signs it with Bitcoin wallet keys. It is a Write operation that commits a trade record, potentially involving cryptocurrency assets. While it involves digital asset transfers (ordinals/sBTC), it is recording an already-completed transfer rather than initiating a financial transaction itself.
From the tool's definition Record a completed inscription transfer on the trade ledger. Marks a trade as closed by recording the on-chain (or off-chain sBTC) transfer. The active wallet signs the record with BIP-137 to prove the transfer was authorized by the sending party.
Attacks that exploit this kind of access
The rule that runs ordinals_p2p_transfer 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_transfer, this is the rule to start with:
ordinals_p2p_transfer stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every ordinals_p2p_transfer call is checked against it from then on.
Questions about ordinals_p2p_transfer
Record a completed inscription transfer on the trade ledger. Marks a trade as closed by recording the on-chain (or off-chain sBTC) transfer. The active wallet signs the record with BIP-137 to prove the transfer was authorized by the sending party. Requires an unlocked wallet with Bitcoin keys. 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 ordinals_p2p_transfer: 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_transfer 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 ordinals_p2p_transfer 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_transfer. 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_transfer 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.
This server
Across the catalogue