Update DNS server settings. Pass key/value pairs for any settings to change (e.g. forwarders, blocking, recursion, cache). Use dns_get_settings first to see current values and available keys.
AI agents use dns_set_settings 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.
The tool modifies DNS server configuration settings (forwarders, blocking rules, recursion behavior, cache parameters). While reversible via subsequent writes, such changes have broad impact on DNS infrastructure behavior and could redirect traffic, disable security controls, or affect all downstream clients.
From the tool's definition Tool name is 'dns_set_settings' and description states 'Update DNS server settings' and 'Pass key/value pairs for any settings to change'. This is explicitly a modification operation affecting server configuration.
Documented attack patterns abuse exactly the kind of access dns_set_settings 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_set_settings:
{
"version": "1",
"default": "deny",
"tools": {
"dns_set_settings": {
"limits": [
{
"counter": "dns_set_settings_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}dns_set_settings 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.
Update DNS server settings. Pass key/value pairs for any settings to change (e.g. forwarders, blocking, recursion, cache). Use dns_get_settings first to see current values and available keys. 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_set_settings: 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_set_settings 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_set_settings 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_set_settings. 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_set_settings 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.