New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

import_domain_zone

Import a domain zone from a remote nameserver

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

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.

More on Linode MCP Server, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Linode MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.