infomaniak_dns_list_records
List every DNS record on a zone managed by Infomaniak. Use the root domain (e.g.
This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-dns-list-records.md
What infomaniak_dns_list_records does on Infomaniak Admin
AI agents call infomaniak_dns_list_records 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_dns_list_records is rated Low
This tool retrieves DNS records from a managed zone without creating, modifying, or deleting any data. It is a read-only operation with minimal blast radius if misused by an AI agent, as it only exposes DNS configuration details that are typically already accessible to the account holder.
From the tool's definition Tool name contains 'list' and description states 'List every DNS record on a zone' — a query operation with no side effects.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs infomaniak_dns_list_records 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_dns_list_records, this is the rule to start with:
infomaniak_dns_list_records 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_dns_list_records call is checked against it from then on.
Questions about infomaniak_dns_list_records
List every DNS record on a zone managed by Infomaniak. Use the root domain (e.g. 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_dns_list_records: 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_dns_list_records 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_dns_list_records 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_dns_list_records. 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_dns_list_records 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