Enable NSEC3 for a DNSSEC domain (prevents zone enumeration)
AI agents use set_dnssec_nsec3 to create or update resources in cPanel MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your cPanel MCP Server environment.
This tool modifies DNS security configuration for a domain by enabling NSEC3 hashing, which is a reversible configuration change. It does not delete or destroy data (not Destructive), does not execute arbitrary code (not Execute), and has no financial impact (not Financial). While DNSSEC misconfigurations could cause DNS resolution failures and broad service disruption, the action itself is Write-category.
From the tool's definition set_dnssec_nsec3 tool enables DNSSEC NSEC3 feature for a domain—'Enable NSEC3 for a DNSSEC domain'
Documented attack patterns abuse exactly the kind of access set_dnssec_nsec3 gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and cPanel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for set_dnssec_nsec3:
{
"version": "1",
"default": "deny",
"tools": {
"set_dnssec_nsec3": {
"limits": [
{
"counter": "set_dnssec_nsec3_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_dnssec_nsec3 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.
Enable NSEC3 for a DNSSEC domain (prevents zone enumeration). It is categorised as a Write tool in the cPanel MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the cPanel MCP Server MCP server in PolicyLayer and add a rule for set_dnssec_nsec3: 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 cPanel MCP Server. Nothing to install.
set_dnssec_nsec3 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 set_dnssec_nsec3 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 set_dnssec_nsec3. 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.
set_dnssec_nsec3 is provided by the cPanel MCP Server MCP server (0xhayd3n/cpanel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from cPanel MCP 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.
164 cPanel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.