Set custom DNS nameservers for a domain
AI agents use namecheap_set_custom_dns to create or update resources in MCP Namecheap Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Namecheap Server environment.
This tool modifies DNS nameserver settings for a domain, which is a reversible configuration change. While DNS changes can have significant operational impact (affecting where traffic is routed), they are not permanently destructive and can be reverted.
From the tool's definition Tool name 'namecheap_set_custom_dns' and description 'Set custom DNS nameservers for a domain' indicate modification of domain DNS configuration.
Documented attack patterns abuse exactly the kind of access namecheap_set_custom_dns gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Namecheap Server, and nothing reaches the server without passing your rules. This is the rule we recommend for namecheap_set_custom_dns:
{
"version": "1",
"default": "deny",
"tools": {
"namecheap_set_custom_dns": {
"limits": [
{
"counter": "namecheap_set_custom_dns_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}namecheap_set_custom_dns stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set custom DNS nameservers for a domain. It is categorised as a Write tool in the MCP Namecheap Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Namecheap Server MCP server in PolicyLayer and add a rule for namecheap_set_custom_dns: 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 MCP Namecheap Server. Nothing to install.
namecheap_set_custom_dns is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the namecheap_set_custom_dns 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 namecheap_set_custom_dns. 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.
namecheap_set_custom_dns is provided by the MCP Namecheap Server MCP server (johnsorrentino/mcp-namecheap). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Namecheap Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 MCP Namecheap Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.