update_personal_nameserver · Spaceship MCP: Risk & Policy

WHAT IT DOES

What update_personal_nameserver does on Spaceship

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

This tool creates or updates glue records that map nameserver hostnames to IP addresses at the registry level. While reversible through deletion or re-update, this is a critical infrastructure modification that affects DNS resolution for an entire domain. Misuse could redirect a domain's DNS to attacker-controlled servers, enabling phishing, malware distribution, or service hijacking.

From the tool's definition Tool description states 'Create or update a personal nameserver host' - uses explicit Write verbs (create, update) to modify nameserver glue records at the registry level.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_personal_nameserver Rate-limited

update_personal_nameserver 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_personal_nameserver": {
      "limits": [
        {
          "counter": "update_personal_nameserver_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_personal_nameserver

What does the update_personal_nameserver tool do? +

Create or update a personal nameserver host with its IP addresses. These are glue records that map a nameserver hostname (e.g. ns1.yourdomain.com) to IP addresses at the registry level. 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_personal_nameserver? +

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

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

Can I rate-limit update_personal_nameserver? +

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

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

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