AI agents call list_personal_nameservers 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.
The tool performs a data retrieval operation (list/query) to display existing nameserver configurations. It has no side effects, does not create, modify, or delete data, and does not execute code or perform financial transactions. This is a straightforward read operation with minimal security risk.
From the tool's definition Tool description states 'List personal (vanity) nameservers' - this is a read-only retrieval operation that queries and returns data about nameserver configuration without modifying any state.
Attacks that exploit this kind of access
List personal (vanity) nameservers configured for a domain (e.g. ns1.yourdomain.com, ns2.yourdomain.com). 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 list_personal_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.
list_personal_nameservers 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 list_personal_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.
Set action: deny in the PolicyLayer policy for list_personal_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.
list_personal_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.
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 →