AI agents call get_verification_records 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 retrieves DNS verification records for inspection purposes. It does not modify, delete, execute, or create any resources—it only queries and returns existing data needed for domain verification. This is a classic Read operation with minimal security risk.
From the tool's definition Tool name 'get_verification_records' and description 'Get the DNS verification records needed to verify ownership' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the DNS verification records needed to verify ownership of SellerHub domain listings. 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_verification_records: 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_verification_records 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_verification_records 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_verification_records. 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_verification_records 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 →