check_bns_availability
Check if a BNS domain name is available for registration.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/check-bns-availability.md
What check_bns_availability does on Aibtc
AI agents call check_bns_availability to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_bns_availability is rated Low
This tool performs a lookup to determine the availability status of a BNS (Bitcoin Name System) domain. It is a read-only query with no side effects—it neither registers the domain nor modifies any state. The blast radius of misuse is minimal, as an agent cannot cause financial harm or irreversible changes through availability checks alone.
From the tool's definition Tool name 'check_bns_availability' and description 'Check if a BNS domain name is available for registration' indicate a query operation that retrieves availability status without creating, modifying, or deleting any data.
Attacks that exploit this kind of access
The rule that runs check_bns_availability 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 check_bns_availability, this is the rule to start with:
check_bns_availability is read-only, so it stays allowed. 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 check_bns_availability call is checked against it from then on.
Questions about check_bns_availability
Check if a BNS domain name is available for registration. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.
Register the Aibtc MCP server in PolicyLayer and add a rule for check_bns_availability: 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.
check_bns_availability is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_bns_availability 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 check_bns_availability. 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.
check_bns_availability 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