arvan_import_dns_zone

Import DNS records from a BIND-style zone file.

SERVERArvanCloud MCP Server SOURCEdwin-gharibi/arvancloud-mcp
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/dwin-gharibi-arvancloud-mcp/arvan-import-dns-zone.md

What arvan_import_dns_zone does on ArvanCloud MCP Server

AI agents use arvan_import_dns_zone to create or update resources in ArvanCloud MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ArvanCloud MCP Server environment.

Why arvan_import_dns_zone is rated Medium

This tool creates or modifies DNS records at scale by importing them from a zone file. While reversible (records can be deleted or updated later), it has significant blast radius: misconfigured DNS imports could redirect traffic, break services, or enable DNS hijacking. A single malicious zone file could compromise the entire DNS infrastructure of multiple domains.

From the tool's definition Import DNS records from a BIND-style zone file — 'import' modifies DNS zone configuration by adding/updating records from an external source

Questions about arvan_import_dns_zone

What does the arvan_import_dns_zone tool do? +

Import DNS records from a BIND-style zone file. It is categorised as a Write tool in the ArvanCloud 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 arvan_import_dns_zone? +

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

What risk level is arvan_import_dns_zone? +

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

Can I rate-limit arvan_import_dns_zone? +

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

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

arvan_import_dns_zone is provided by the ArvanCloud MCP Server MCP server (dwin-gharibi/arvancloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ArvanCloud 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 ArvanCloud 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.