Allow a domain name, bypassing any block lists. Useful for whitelisting false positives.
AI agents use dns_allow_domain to create or update resources in Technitium MCP Secure — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Technitium MCP Secure environment.
This tool modifies the DNS server's block list configuration by adding a domain to an allowlist/whitelist. It creates or updates a policy entry, which is a reversible write operation. Misuse could allow malicious domains to bypass security filtering, giving it medium severity.
From the tool's definition Allow a domain name, bypassing any block lists. Useful for whitelisting false positives.
Documented attack patterns abuse exactly the kind of access dns_allow_domain gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Technitium MCP Secure, and nothing reaches the server without passing your rules. This is the rule we recommend for dns_allow_domain:
{
"version": "1",
"default": "deny",
"tools": {
"dns_allow_domain": {
"limits": [
{
"counter": "dns_allow_domain_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}dns_allow_domain 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.
Allow a domain name, bypassing any block lists. Useful for whitelisting false positives. It is categorised as a Write tool in the Technitium MCP Secure MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Technitium MCP Secure MCP server in PolicyLayer and add a rule for dns_allow_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 Technitium MCP Secure. Nothing to install.
dns_allow_domain 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 dns_allow_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 dns_allow_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.
dns_allow_domain is provided by the Technitium MCP Secure MCP server (rosschurchill/technitium-mcp-secure). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Technitium MCP Secure, 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.
39 Technitium MCP Secure tools catalogued and risk-classified — across an index of 43,000+ MCP servers.