import_domain_zone
Import a domain zone from a remote nameserver
This record as markdown: /tools/takashito-linode-mcp-server/import-domain-zone.md
What import_domain_zone does on Linode MCP Server
AI agents use import_domain_zone to create or update resources in Linode MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linode MCP Server environment.
Why import_domain_zone is rated Medium
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.
Attacks that exploit this kind of access
The rule that runs import_domain_zone safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_domain_zone, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every import_domain_zone call is checked against it from then on.
Questions about import_domain_zone
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.
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.
import_domain_zone is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on Linode MCP Server, and thousands of servers like it.
This server
Across the catalogue