Verify the TXT and route DNS records for a custom domain. Use this after the user says the DNS records are added.
AI agents call verify_custom_domain to retrieve information from PlugLayer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs DNS record verification only, which is a passive check operation. It retrieves and validates existing DNS records but does not create, modify, or delete any infrastructure or data. Even though it operates in an infrastructure management context, the specific action (verify) is clearly read-only with no side effects.
From the tool's definition Tool description states 'Verify the TXT and route DNS records' — verification is a read operation that checks/queries DNS record status without modifying anything.
Attacks that exploit this kind of access
Verify the TXT and route DNS records for a custom domain. Use this after the user says the DNS records are added. It is categorised as a Read tool in the PlugLayer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PlugLayer MCP Server MCP server in PolicyLayer and add a rule for verify_custom_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 PlugLayer MCP Server. Nothing to install.
verify_custom_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_custom_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_custom_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_custom_domain is provided by the PlugLayer MCP Server MCP server (pluglayer/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 →