gandi_livedns_update_snapshot · Gandi MCP: Risk & Policy

WHAT IT DOES

What gandi_livedns_update_snapshot does on Gandi

AI agents use gandi_livedns_update_snapshot 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_snapshot needs a policy

The tool performs a Write operation—it modifies DNS snapshot data reversibly. Within a DNS management context (Gandi LiveDNS), snapshots are typically backups or saved states that can be created, modified, or restored. While not destructive (snapshots are usually restorable), updating snapshots could affect DNS operations if a malicious update replaces critical configurations.

From the tool's definition Tool name 'gandi_livedns_update_snapshot' indicates modification of DNS snapshot state. The verb 'update' and context within a production DNS management system (LiveDNS) suggests creation or modification of DNS configuration snapshots.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gandi_livedns_update_snapshot Rate-limited

gandi_livedns_update_snapshot 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_snapshot": {
      "limits": [
        {
          "counter": "gandi_livedns_update_snapshot_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_snapshot

What does the gandi_livedns_update_snapshot tool do? +

gandi_livedns_update_snapshot. 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_snapshot? +

Register the Gandi MCP server in PolicyLayer and add a rule for gandi_livedns_update_snapshot: 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_snapshot? +

gandi_livedns_update_snapshot 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_snapshot? +

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

Set action: deny in the PolicyLayer policy for gandi_livedns_update_snapshot. 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_snapshot? +

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