Compare a list of expected DNS records against the actual records configured in Spaceship. Returns which expected records are missing and which unexpected records exist. Useful for verifying DNS configurations match your infrastructure requirements.
AI agents call check_dns_alignment 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 performs a diagnostic comparison of DNS records—retrieving actual records from Spaceship and comparing them against expected values. No data is created, modified, or deleted; no code is executed; no financial transactions occur. It is purely informational and non-destructive, fitting the Read category.
From the tool's definition Tool compares and returns DNS record information ("Returns which expected records are missing and which unexpected records exist"). It reads and queries existing DNS configurations without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
Compare a list of expected DNS records against the actual records configured in Spaceship. Returns which expected records are missing and which unexpected records exist. Useful for verifying DNS configurations match your infrastructure requirements. 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 check_dns_alignment: 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.
check_dns_alignment 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 check_dns_alignment 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 check_dns_alignment. 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.
check_dns_alignment 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 →