dns_get_stats

THE RISK

Low Risk

Why dns_get_stats needs a policy

This tool queries historical statistics and diagnostic data without side effects. It is a safe read operation that gathers observability information about DNS server performance. Even if an AI agent misuses it, the worst outcome is information disclosure about DNS traffic patterns, which poses minimal risk compared to record creation/deletion or zone management tools on this server.

From the tool's definition Tool retrieves DNS query statistics, returning counts and top lists (top clients, top domains, top blocked domains). The description uses purely retrieval language: 'Get', 'Returns'. No modification, deletion, or execution of external operations occurs.

Documented attack patterns abuse exactly the kind of access dns_get_stats gives an agent:

POLICY

How to control dns_get_stats

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_get_stats:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dns_get_stats": {}
  }
}

dns_get_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Technitium MCP Secure — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Technitium MCP Secure tools

Destructive dns_delete_cached Delete a specific domain from the DNS cache. Unlike flush, this only removes the specified Destructive dns_delete_record Delete a specific DNS record from a zone. Requires confirm=true to execute. Destructive dns_delete_zone Delete a DNS zone and all its records. Requires confirm=true to execute. Destructive dns_remove_allowed Remove a domain from the allow list. The domain will no longer bypass block lists. Destructive dns_uninstall_app Uninstall a DNS app from the server. Requires confirm=true to execute. Destructive dns_flush_allowed Flush the entire allow list. All allowed domains will be removed. Requires confirm=true to Destructive dns_flush_blocked Flush the entire custom block list. All manually blocked domains will be removed. Requires Execute dns_flush_cache Flush the entire DNS cache. Forces all subsequent queries to be resolved fresh from upstre

All 39 Technitium MCP Secure tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about dns_get_stats

What does the dns_get_stats tool do? +

Get DNS query statistics for a time period. Returns total queries, cached, blocked, failure counts, plus top clients, top domains, and top blocked domains. It is categorised as a Read tool in the Technitium MCP Secure MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on dns_get_stats? +

Register the Technitium MCP Secure MCP server in PolicyLayer and add a rule for dns_get_stats: 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.

What risk level is dns_get_stats? +

dns_get_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dns_get_stats? +

Yes. Add a rate_limit block to the dns_get_stats 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.

How do I block dns_get_stats completely? +

Set action: deny in the PolicyLayer policy for dns_get_stats. 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.

What MCP server provides dns_get_stats? +

dns_get_stats 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.

Enforce policy on every Technitium MCP Secure tool call.

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.

CHECK YOUR STACK →