Start or check domain DNS verification. Call with domain to start (returns TXT record to add), call without to check status.
AI agents call verify_domain to retrieve information from Lightpaper Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The primary actions are initiating a DNS TXT record lookup and checking verification status, both of which are essentially read/query operations against DNS records. While it 'starts' a verification process, it does not write, modify, or delete any user data — it returns a TXT record to add (informational) and checks status. No destructive, financial, or irreversible effects.
From the tool's definition 'Start or check domain DNS verification' and 'call without to check status' — the tool initiates or polls a DNS verification process
Attacks that exploit this kind of access
Start or check domain DNS verification. Call with domain to start (returns TXT record to add), call without to check status. It is categorised as a Read tool in the Lightpaper Mcp MCP Server, which means it retrieves data without modifying state.
Register the Lightpaper MCP server in PolicyLayer and add a rule for verify_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 Lightpaper Mcp. Nothing to install.
verify_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 verify_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 verify_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.
verify_domain is provided by the Lightpaper MCP server (pypi:lightpaper-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 →