AI agents call get_domain 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 queries and returns domain metadata without modifying, deleting, or executing any operations. It is a straightforward read operation with minimal risk — the data returned is generally non-sensitive operational metadata that a domain owner would routinely access. Low severity because exposure does not enable financial transactions, code execution, or destructive actions.
From the tool's definition Tool retrieves 'detailed information about a specific domain including registration/expiration dates, auto-renewal status, privacy protection level, nameservers, lifecycle status, and contacts.' The verb 'Get' and the nature of returned data (dates, statuses,…
Attacks that exploit this kind of access
Get detailed information about a specific domain including registration/expiration dates, auto-renewal status, privacy protection level, nameservers, lifecycle status, and contacts. 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_domain: 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_domain 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_domain 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_domain. 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_domain 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 →