gandi_domain_disable_livedns_dnssec

WHAT IT DOES

What gandi_domain_disable_livedns_dnssec does on Gandi

AI agents use gandi_domain_disable_livedns_dnssec 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_domain_disable_livedns_dnssec needs a policy

The tool modifies domain DNS security settings by disabling DNSSEC, which is a reversible write operation. While it disables a security feature (creating potential exposure), it does not delete data or prevent undo—the feature can be re-enabled. This is categorized as Write rather than Destructive because DNSSEC can be re-enabled.

From the tool's definition Disable LiveDNS-managed DNSSEC for a domain - this modifies domain configuration by disabling a security feature (DNSSEC), which is a configuration change that affects DNS resolution behavior.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gandi_domain_disable_livedns_dnssec Rate-limited

gandi_domain_disable_livedns_dnssec 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_domain_disable_livedns_dnssec": {
      "limits": [
        {
          "counter": "gandi_domain_disable_livedns_dnssec_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_domain_disable_livedns_dnssec

What does the gandi_domain_disable_livedns_dnssec tool do? +

Disable LiveDNS-managed DNSSEC for a domain. 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_domain_disable_livedns_dnssec? +

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

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

Can I rate-limit gandi_domain_disable_livedns_dnssec? +

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

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

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