create_a_record · Spaceship MCP: Risk & Policy

WHAT IT DOES

What create_a_record does on Spaceship

AI agents use create_a_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_a_record needs a policy

This tool creates DNS records that map domain names to IPv4 addresses. While creation is technically reversible (records can be deleted or modified), misconfiguration or malicious use could redirect traffic, disrupt services, or enable phishing attacks. This is Write rather than Execute because the tool itself does not run arbitrary code—it modifies a specific data resource (DNS records).

From the tool's definition Tool name 'create_a_record' and description 'Create an A record (IPv4 address) for a domain' indicate this creates/modifies DNS records, which are reversible but have significant impact on domain routing and availability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_a_record Rate-limited

create_a_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_a_record": {
      "limits": [
        {
          "counter": "create_a_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_a_record

What does the create_a_record tool do? +

Create an A record (IPv4 address) 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_a_record? +

Register the Spaceship MCP server in PolicyLayer and add a rule for create_a_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_a_record? +

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

Can I rate-limit create_a_record? +

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

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

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