TLD registry + Public Suffix List intelligence. tld=io returns IANA root-zone metadata (type, managing organization, unicode form). domain=shop.example.co.uk runs the full PSL algorithm: effective public suffix, registrable domain, subdomain, matched rule, and whether the suffix is ICANN or priva...
AI agents call tld.info to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read/query tool that retrieves and analyzes publicly available TLD and domain registry information. It parses domain names to extract structural metadata and applies the Public Suffix List algorithm, but produces no side effects—no data is created, modified, deleted, or financial operations performed.
From the tool's definition Tool description explicitly states it 'returns IANA root-zone metadata' and 'runs the full PSL algorithm' to provide information about TLD structure, public suffix lists, and domain parsing. No modification, deletion, or code execution capabilities mentioned.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
TLD registry + Public Suffix List intelligence. tld=io returns IANA root-zone metadata (type, managing organization, unicode form). domain=shop.example.co.uk runs the full PSL algorithm: effective public suffix, registrable domain, subdomain, matched rule, and whether the suffix is ICANN or private/corporate (github.io, s3.amazonaws.com). For cookie scoping, per-registrant rate limiting, URL dedup, and abuse analysis. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for tld.info: 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 Mcp. Nothing to install.
tld.info 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 tld.info 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 tld.info. 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.
tld.info is provided by the MCP server (@2sio/mcp). 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 →