import_domain_zone

THE RISK

Medium Risk

Why import_domain_zone needs a policy

This tool creates or modifies domain zone data in Linode's DNS system. While not immediately destructive (can theoretically be reversed by re-importing), it directly alters DNS zone configuration which could redirect domain traffic, affect email routing, or disrupt services if misused.

From the tool's definition Tool name 'import_domain_zone' and description 'Import a domain zone from a remote nameserver' indicate the tool modifies DNS/domain configuration by importing zone data, creating or updating records.

Documented attack patterns abuse exactly the kind of access import_domain_zone gives an agent:

POLICY

How to control import_domain_zone

PolicyLayer is an MCP gateway — it sits between your AI agents and Linode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for import_domain_zone:

policy.json

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

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

Create a free account and register Linode MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Linode MCP Server tools

Destructive cancel_account Cancel your account Destructive cancel_backups Cancel backups for a Linode instance Destructive cancel_object_storage Cancel Object Storage service Destructive delete_alert_definition Delete an alert definition Destructive delete_api_token Delete an API token Destructive delete_config_interface Delete an interface from a configuration profile Destructive delete_domain Delete a domain Destructive delete_domain_record Delete a domain record

All 416 Linode MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about import_domain_zone

What does the import_domain_zone tool do? +

Import a domain zone from a remote nameserver. It is categorised as a Write tool in the Linode MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on import_domain_zone? +

Register the Linode MCP Server MCP server in PolicyLayer and add a rule for import_domain_zone: 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 Linode MCP Server. Nothing to install.

What risk level is import_domain_zone? +

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

Can I rate-limit import_domain_zone? +

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

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

import_domain_zone is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Linode MCP Server tool call.

Start from Linode MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →