reverse_bns_lookup
Get the BNS domain names owned by an address.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/reverse-bns-lookup.md
What reverse_bns_lookup does on Aibtc
AI agents call reverse_bns_lookup 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 reverse_bns_lookup is rated Low
This tool retrieves information (BNS domain names) associated with a blockchain address. It performs a query operation that does not modify, create, delete, or execute anything. The action is purely informational and has no side effects on the blockchain or any system state.
From the tool's definition Tool description: 'Get the BNS domain names owned by an address.' The verb 'Get' and the read-only nature of a lookup operation indicate data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs reverse_bns_lookup 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 reverse_bns_lookup, this is the rule to start with:
reverse_bns_lookup 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 reverse_bns_lookup call is checked against it from then on.
Questions about reverse_bns_lookup
Get the BNS domain names owned by an address. 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 reverse_bns_lookup: 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.
reverse_bns_lookup 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 reverse_bns_lookup 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 reverse_bns_lookup. 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.
reverse_bns_lookup 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