list_user_domains
List all BNS domains owned by an address.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/list-user-domains.md
What list_user_domains does on Aibtc
AI agents call list_user_domains 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 list_user_domains is rated Low
This tool performs a read-only lookup of blockchain domains (BNS) associated with a given address. It retrieves existing information without creating, modifying, deleting, or executing any operations. The blast radius is minimal—misuse only exposes publicly available domain ownership information.
From the tool's definition Tool name 'list_user_domains' and description 'List all BNS domains owned by an address' indicate a query operation that retrieves and returns data without modifying state.
Attacks that exploit this kind of access
The rule that runs list_user_domains 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 list_user_domains, this is the rule to start with:
list_user_domains 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 list_user_domains call is checked against it from then on.
Questions about list_user_domains
List all BNS domains 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 list_user_domains: 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.
list_user_domains 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 list_user_domains 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 list_user_domains. 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.
list_user_domains 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