get_domain_auth_code
Get domain EPP auth code for outbound transfers
This record as markdown: /tools/cbrown35-20i-mcp/get-domain-auth-code.md
What get_domain_auth_code does on 20i MCP Server
AI agents call get_domain_auth_code to retrieve information from 20i MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_domain_auth_code is rated Low
Classified as Read because the tool's primary function is to retrieve existing data (EPP auth code) without creating, modifying, or deleting resources. Severity is medium rather than low because EPP auth codes are security-sensitive credentials that could enable unauthorized domain transfers if disclosed to an attacker, creating moderate blast radius.
From the tool's definition Tool retrieves domain EPP auth code via 'Get' operation. EPP (Extensible Provisioning Protocol) auth codes are sensitive credentials required for domain transfers, but the tool only reads/retrieves this information without modifying hosting infrastructure.
Attacks that exploit this kind of access
The rule that runs get_domain_auth_code safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_domain_auth_code, this is the rule to start with:
get_domain_auth_code 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 20i MCP Server, apply this rule, and every get_domain_auth_code call is checked against it from then on.
Questions about get_domain_auth_code
Get domain EPP auth code for outbound transfers. It is categorised as a Read tool in the 20i MCP Server MCP Server, which means it retrieves data without modifying state.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for get_domain_auth_code: 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 20i MCP Server. Nothing to install.
get_domain_auth_code 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 get_domain_auth_code 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 get_domain_auth_code. 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.
get_domain_auth_code is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
This server
Across the catalogue