update_nameservers · Spaceship MCP: Risk & Policy

WHAT IT DOES

What update_nameservers does on Spaceship

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

This tool creates or modifies critical domain infrastructure (nameservers) reversibly, fitting the Write category. Severity is high because misconfiguring nameservers can render a domain inaccessible or redirect it maliciously, creating significant blast radius if an AI agent misuses it with wrong values. However, it is not Destructive since the changes are fully reversible and no data is deleted.

From the tool's definition Tool description explicitly states 'Update the nameservers for a domain' and 'replaces ALL current nameservers with the provided list.' The action modifies DNS configuration but is reversible—nameservers can be changed back to previous values.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_nameservers Rate-limited

update_nameservers 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": {
    "update_nameservers": {
      "limits": [
        {
          "counter": "update_nameservers_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 update_nameservers

What does the update_nameservers tool do? +

Update the nameservers for a domain. This replaces ALL current nameservers with the provided list. 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 update_nameservers? +

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

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

Can I rate-limit update_nameservers? +

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

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

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