arvan_create_cname_record

Convenience: create a CNAME record from name to target.

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-create-cname-record.md

What arvan_create_cname_record does on ArvanCloud MCP Server

AI agents use arvan_create_cname_record 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_create_cname_record is rated Medium

This tool writes DNS records, which is a reversible modification. While destructive deletion is not possible here, creating CNAME records can redirect traffic, potentially disrupting services or enabling DNS hijacking if misused by an agent. The high severity reflects the blast radius of DNS misconfiguration in production environments.

From the tool's definition Creates a CNAME record (DNS modification). The action 'create' is explicitly stated, and CNAME records are fundamental DNS configuration entries that route domain names to targets.

Questions about arvan_create_cname_record

What does the arvan_create_cname_record tool do? +

Convenience: create a CNAME record from name to target. 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_create_cname_record? +

Register the ArvanCloud MCP Server MCP server in PolicyLayer and add a rule for arvan_create_cname_record: 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_create_cname_record? +

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

Can I rate-limit arvan_create_cname_record? +

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

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

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

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