get_dns_analytics

Get DNS query analytics and performance data

SERVER20i MCP Server SOURCEcbrown35/20i-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cbrown35-20i-mcp/get-dns-analytics.md

WHAT IT DOES

What get_dns_analytics does on 20i MCP Server

AI agents call get_dns_analytics to retrieve information from 20i MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_dns_analytics is rated Low

This tool queries and retrieves DNS analytics and performance metrics. It performs a read-only operation on monitoring/analytics data without creating, modifying, deleting, or executing anything. The blast radius of misuse is limited to information disclosure about DNS query patterns.

From the tool's definition Tool name 'get_dns_analytics' and description 'Get DNS query analytics and performance data' indicate retrieval of existing data with no modification, deletion, or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_dns_analytics safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dns_analytics, this is the rule to start with:

get_dns_analytics Allowed

get_dns_analytics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every get_dns_analytics call is checked against it from then on.

FAQ

Questions about get_dns_analytics

What does the get_dns_analytics tool do? +

Get DNS query analytics and performance data. It is categorised as a Read tool in the 20i MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_dns_analytics? +

Register the 20i MCP Server MCP server in PolicyLayer and add a rule for get_dns_analytics: 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 20i MCP Server. Nothing to install.

What risk level is get_dns_analytics? +

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

Can I rate-limit get_dns_analytics? +

Yes. Add a rate_limit block to the get_dns_analytics 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 get_dns_analytics completely? +

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

get_dns_analytics is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 20i MCP Server, and thousands of servers like it.

This server

All 302 20i MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →