infomaniak_get_domain_full
Full domain detail including auth_code (EPP transfer code), transfer_status, trade_status, termination state, glue records, TLD/registry info, attached service (web hosting), DNS detail, DNS health diagnostic, owner (registrant), associated products on the domain AND its subdomains, and the DNS l...
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-get-domain-full.md
What infomaniak_get_domain_full does on Infomaniak Admin
AI agents call infomaniak_get_domain_full to retrieve information from Infomaniak Admin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why infomaniak_get_domain_full is rated Low
This is fundamentally a Read operation—it queries and retrieves domain details without side effects. However, severity is elevated to 'medium' rather than 'low' because the returned data includes sensitive information (auth_code/EPP transfer code, owner/registrant details, and transfer/trade status) that could enable domain hijacking, unauthorized transfers, or social engineering if exposed to an unauthorized agent.
From the tool's definition Tool retrieves comprehensive domain information including auth_code (EPP transfer code), transfer_status, trade_status, termination state, glue records, TLD/registry info, attached services, DNS detail, DNS health diagnostic, owner data, associated products,…
Attacks that exploit this kind of access
The rule that runs infomaniak_get_domain_full safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Infomaniak Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For infomaniak_get_domain_full, this is the rule to start with:
infomaniak_get_domain_full 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 Infomaniak Admin, apply this rule, and every infomaniak_get_domain_full call is checked against it from then on.
Questions about infomaniak_get_domain_full
Full domain detail including auth_code (EPP transfer code), transfer_status, trade_status, termination state, glue records, TLD/registry info, attached service (web hosting), DNS detail, DNS health diagnostic, owner (registrant), associated products on the domain AND its subdomains, and the DNS logs API URL. Accepts either domain_id or FQDN. Manager-private. It is categorised as a Read tool in the Infomaniak Admin MCP Server, which means it retrieves data without modifying state.
Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_get_domain_full: 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 Infomaniak Admin. Nothing to install.
infomaniak_get_domain_full 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 infomaniak_get_domain_full 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 infomaniak_get_domain_full. 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.
infomaniak_get_domain_full is provided by the Infomaniak Admin MCP server (henrikogaard/infomaniak-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Infomaniak Admin, and thousands of servers like it.
This server
Across the catalogue