infomaniak_dns_delete_record

Delete a DNS record from an Infomaniak-managed zone. Two-phase commit: first call returns a plan with a preview of the record to delete + token, second call (same params + token) actually deletes.

SERVERInfomaniak Admin SOURCEhenrikogaard/infomaniak-admin-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/henrikogaard-infomaniak-admin-mcp/infomaniak-dns-delete-record.md

WHAT IT DOES

What infomaniak_dns_delete_record does on Infomaniak Admin

AI agents call infomaniak_dns_delete_record to permanently remove resources in Infomaniak Admin, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why infomaniak_dns_delete_record is rated Critical

This tool irreversibly deletes DNS records, making it Destructive rather than Write. DNS records are critical infrastructure components; deleting them can break email delivery, website accessibility, and other services. While the two-phase commit mitigates accidental misuse by requiring explicit confirmation, the underlying action is permanent deletion.

From the tool's definition Delete a DNS record from an Infomaniak-managed zone. The tool explicitly performs deletion of DNS records, which are configuration data that cannot be easily recovered once removed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs infomaniak_dns_delete_record 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_delete_record, this is the rule to start with:

infomaniak_dns_delete_record Hidden

infomaniak_dns_delete_record is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "infomaniak_dns_delete_record"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Infomaniak Admin, apply this rule, and every infomaniak_dns_delete_record call is checked against it from then on.

FAQ

Questions about infomaniak_dns_delete_record

What does the infomaniak_dns_delete_record tool do? +

Delete a DNS record from an Infomaniak-managed zone. Two-phase commit: first call returns a plan with a preview of the record to delete + token, second call (same params + token) actually deletes. It is categorised as a Destructive tool in the Infomaniak Admin MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on infomaniak_dns_delete_record? +

Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_dns_delete_record: 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.

What risk level is infomaniak_dns_delete_record? +

infomaniak_dns_delete_record is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit infomaniak_dns_delete_record? +

Yes. Add a rate_limit block to the infomaniak_dns_delete_record 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.

How do I block infomaniak_dns_delete_record completely? +

Set action: deny in the PolicyLayer policy for infomaniak_dns_delete_record. 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.

What MCP server provides infomaniak_dns_delete_record? +

infomaniak_dns_delete_record 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.

KEEP EXPLORING

More on Infomaniak Admin, and thousands of servers like it.

This server

All 217 Infomaniak Admin tools → Critical-risk tools on this server →

Across the catalogue

delete_dns_record on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →