infomaniak_dns_create_record

Create a DNS record on an Infomaniak-managed zone. Two-phase commit: first call returns a plan + token, second call (same params + token) actually creates the record.

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-create-record.md

WHAT IT DOES

What infomaniak_dns_create_record does on Infomaniak Admin

AI agents use infomaniak_dns_create_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_create_record is rated Medium

Creating a DNS record is a reversible write operation that modifies domain configuration. It is not destructive (can be deleted), not execute (does not run arbitrary code), and not financial. The two-phase commit reduces operational risk but the tool's core function remains data creation/modification.

From the tool's definition Tool description states 'Create a DNS record' which is a data modification operation. The two-phase commit mechanism (plan + token confirmation) is a safeguard but does not change the fundamental action category.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

infomaniak_dns_create_record Rate-limited

infomaniak_dns_create_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_create_record": {
      "limits": [
        {
          "counter": "infomaniak_dns_create_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_create_record call is checked against it from then on.

FAQ

Questions about infomaniak_dns_create_record

What does the infomaniak_dns_create_record tool do? +

Create a DNS record on an Infomaniak-managed zone. Two-phase commit: first call returns a plan + token, second call (same params + token) actually creates the record. 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_create_record? +

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

infomaniak_dns_create_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_create_record? +

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

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

infomaniak_dns_create_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 →create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

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