create_cname_record · Spaceship MCP: Risk & Policy

WHAT IT DOES

What create_cname_record does on Spaceship

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

WHY IT NEEDS A POLICY

Why create_cname_record needs a policy

Creating DNS records is a reversible write operation that modifies domain configuration. CNAME records can redirect traffic and affect domain resolution, making unauthorized creation a significant security risk if an AI agent is compromised or misdirected. However, it is not destructive (records can be deleted/modified later) and does not directly execute code or move money.

From the tool's definition Tool name explicitly states 'create_cname_record' and description confirms it 'Create[s] a CNAME record'. CNAME records are DNS resource records that create canonical name aliases.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_cname_record Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Spaceship, so you can run agents against it safely.

FAQ

Questions about create_cname_record

What does the create_cname_record tool do? +

Create a CNAME record (canonical name/alias) for a domain. It is categorised as a Write tool in the Spaceship MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_cname_record? +

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

What risk level is create_cname_record? +

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 create_cname_record? +

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

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

create_cname_record is provided by the Spaceship MCP server (naveenkm007/spaceship-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.