save_dns_records · Spaceship MCP: Risk & Policy

WHAT IT DOES

What save_dns_records does on Spaceship

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

This tool modifies DNS records, which is a Write operation (data is created or updated reversibly). It is not Destructive because upsert operations can theoretically be undone by resetting records. Severity is high because misconfigured DNS can disrupt domain functionality, email delivery, and service availability, though the effects are technically reversible.

From the tool's definition Tool description states 'Save (upsert) DNS records for a domain using PUT with force overwrite.' The terms 'upsert' (update/insert) and 'PUT' indicate modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

save_dns_records Rate-limited

save_dns_records 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": {
    "save_dns_records": {
      "limits": [
        {
          "counter": "save_dns_records_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 save_dns_records

What does the save_dns_records tool do? +

Save (upsert) DNS records for a domain using PUT with force overwrite. 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 save_dns_records? +

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

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

Can I rate-limit save_dns_records? +

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

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

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