AI agents call get_personal_nameserver to retrieve information from Spaceship without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves nameserver configuration information. It queries existing data about a vanity nameserver without creating, modifying, deleting, executing commands, or performing financial operations. The blast radius of misuse is minimal—an attacker could enumerate nameserver details but cannot alter DNS infrastructure or cause irreversible harm through this tool alone.
From the tool's definition Tool name includes 'get_' and description states 'Get details of a single personal nameserver', indicating data retrieval with no modification or side effects. Returns read-only information: hostname and IP addresses.
Attacks that exploit this kind of access
Get details of a single personal (vanity) nameserver by hostname, including its IP addresses. It is categorised as a Read tool in the Spaceship MCP Server, which means it retrieves data without modifying state.
Register the Spaceship MCP server in PolicyLayer and add a rule for get_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.
get_personal_nameserver is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →