List all registered domains for the authenticated account. Requires TETHER_API_KEY. Use domain IDs when creating agents with domain assignment.
AI agents call list_domains to retrieve information from Tether Name without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and lists existing domain data without modifying, deleting, or executing any operations. It is purely informational, returning a read-only view of domains associated with the authenticated account. The blast radius of misuse is limited to information disclosure about domains, hence low severity.
From the tool's definition Tool description states 'List all registered domains for the authenticated account.' This is a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all registered domains for the authenticated account. Requires TETHER_API_KEY. Use domain IDs when creating agents with domain assignment. It is categorised as a Read tool in the Tether Name MCP Server, which means it retrieves data without modifying state.
Register the Tether Name MCP server in PolicyLayer and add a rule for list_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 Tether Name. Nothing to install.
list_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_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_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_domains is provided by the Tether Name MCP server (tether-name-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →