List blocked DNS zones (domains that are denied). Returns a hierarchical tree — call with no domain to see top-level zones, then pass a domain (e.g.
AI agents call dns_list_blocked to retrieve information from Technitium MCP Secure without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation because it retrieves DNS blocking policy information without modifying any state. However, severity is elevated to 'high' rather than 'low' because the blocked domains list reveals the DNS filtering/security policy configuration of the organization.
From the tool's definition 'List blocked DNS zones (domains that are denied)' — retrieves and queries data with no modification. The tool returns information about blocked domains in a hierarchical structure. No side effects or mutations occur.
Documented attack patterns abuse exactly the kind of access dns_list_blocked 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_list_blocked:
{
"version": "1",
"default": "deny",
"tools": {
"dns_list_blocked": {}
}
} dns_list_blocked is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List blocked DNS zones (domains that are denied). Returns a hierarchical tree — call with no domain to see top-level zones, then pass a domain (e.g. It is categorised as a Read tool in the Technitium MCP Secure MCP Server, which means it retrieves data without modifying state.
Register the Technitium MCP Secure MCP server in PolicyLayer and add a rule for dns_list_blocked: 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_list_blocked 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 dns_list_blocked 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_list_blocked. 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_list_blocked 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.