infomaniak_dns_update_record

Update one or more fields of a DNS record. Two-phase commit: first call shows current vs proposed values + token; second call (same params + token) applies the update.

SERVERInfomaniak Admin SOURCEhenrikogaard/infomaniak-admin-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What infomaniak_dns_update_record does on Infomaniak Admin

AI agents use infomaniak_dns_update_record to create or update resources in Infomaniak Admin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Infomaniak Admin environment.

RISK

Why infomaniak_dns_update_record is rated Medium

DNS record updates are Write operations—they create or modify data reversibly. The two-phase commit pattern confirms user intent before applying changes. While DNS modifications can have broad impact (affecting domain routing and services), the operation itself is reversible and does not irreversibly delete data, making it Write rather than Destructive.

From the tool's definition Tool description states it "Update[s] one or more fields of a DNS record" and implements a "Two-phase commit" pattern where changes are proposed first then applied. This is a reversible modification operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

infomaniak_dns_update_record Rate-limited

infomaniak_dns_update_record stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "infomaniak_dns_update_record": {
      "limits": [
        {
          "counter": "infomaniak_dns_update_record_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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_update_record call is checked against it from then on.

FAQ

Questions about infomaniak_dns_update_record

What does the infomaniak_dns_update_record tool do? +

Update one or more fields of a DNS record. Two-phase commit: first call shows current vs proposed values + token; second call (same params + token) applies the update. It is categorised as a Write tool in the Infomaniak Admin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on infomaniak_dns_update_record? +

Register the Infomaniak Admin MCP server in PolicyLayer and add a rule for infomaniak_dns_update_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_update_record? +

infomaniak_dns_update_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit infomaniak_dns_update_record? +

Yes. Add a rate_limit block to the infomaniak_dns_update_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_update_record completely? +

Set action: deny in the PolicyLayer policy for infomaniak_dns_update_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_update_record? +

infomaniak_dns_update_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 →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →