gandi_livedns_update_record · Gandi MCP: Risk & Policy

WHAT IT DOES

What gandi_livedns_update_record does on Gandi

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

WHY IT NEEDS A POLICY

Why gandi_livedns_update_record needs a policy

DNS record updates are Write operations—they modify configuration data reversibly but can have significant impact on domain routing, email delivery, and service availability if misconfigured by an agent. High severity due to blast radius (affecting live infrastructure), though confidence is moderately reduced by the lack of descriptive text.

From the tool's definition Tool name 'gandi_livedns_update_record' explicitly indicates modification of DNS records. The 'update' verb combined with 'livedns_record' context signifies reversible data modification. Description is empty, reducing confidence slightly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gandi_livedns_update_record Rate-limited

gandi_livedns_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": {
    "gandi_livedns_update_record": {
      "limits": [
        {
          "counter": "gandi_livedns_update_record_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Gandi, so you can run agents against it safely.

FAQ

Questions about gandi_livedns_update_record

What does the gandi_livedns_update_record tool do? +

gandi_livedns_update_record. It is categorised as a Write tool in the Gandi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gandi_livedns_update_record? +

Register the Gandi MCP server in PolicyLayer and add a rule for gandi_livedns_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 Gandi. Nothing to install.

What risk level is gandi_livedns_update_record? +

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

Can I rate-limit gandi_livedns_update_record? +

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

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

gandi_livedns_update_record is provided by the Gandi MCP server (millsymills-com/gandi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.