bns_register
Register a BNS name via Stacks contract call.
This record as markdown: /tools/markmhendrickson-mcp-server-bitcoin/bns-register.md
What bns_register does on Bitcoin wallet MCP server
AI agents use bns_register to commit financial operations through Bitcoin wallet MCP server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why bns_register is rated Critical
Registering a BNS (Bitcoin Name System) name involves a blockchain transaction that commits financial resources (STX tokens as registration fees) on the Stacks network. This is an irreversible on-chain operation with financial obligation, making Financial the most severe applicable category. Misuse could result in unintended spending of cryptocurrency funds.
From the tool's definition Register a BNS name via Stacks contract call
Attacks that exploit this kind of access
The rule that runs bns_register safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bitcoin wallet MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bns_register, this is the rule to start with:
Any call to bns_register is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Bitcoin wallet MCP server, apply this rule, and every bns_register call is checked against it from then on.
Questions about bns_register
Register a BNS name via Stacks contract call. It is categorised as a Financial tool in the Bitcoin wallet MCP server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Bitcoin wallet MCP server MCP server in PolicyLayer and add a rule for bns_register: 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 Bitcoin wallet MCP server. Nothing to install.
bns_register 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 bns_register 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 bns_register. 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.
bns_register is provided by the Bitcoin wallet MCP server MCP server (markmhendrickson/mcp-server-bitcoin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bitcoin wallet MCP server, and thousands of servers like it.
Across the catalogue