Detect the likely DNS/domain provider for a custom domain from public NS records so the agent can confirm it with the user before showing tailored DNS steps.
AI agents call detect_custom_domain_provider 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 queries public DNS records to determine which provider manages a domain's nameservers. It is informational only—it neither modifies infrastructure, executes code with side effects, creates/deletes resources, nor involves financial transactions. The data retrieved (NS records) is publicly available and the operation produces no state changes.
From the tool's definition The tool 'detect_custom_domain_provider' performs a lookup of public NS (nameserver) records to identify a domain's DNS provider. This is a read-only query operation that retrieves public information from DNS records with no side effects or modifications.
Attacks that exploit this kind of access
Detect the likely DNS/domain provider for a custom domain from public NS records so the agent can confirm it with the user before showing tailored DNS steps. 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 detect_custom_domain_provider: 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.
detect_custom_domain_provider 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 detect_custom_domain_provider 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 detect_custom_domain_provider. 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.
detect_custom_domain_provider 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 →