Read-only fetch of public IntoDNS.ai usage counters: total scans run, security checks performed, hall-of-fame entries, and rolling daily/weekly aggregates. Returns plain integer counters with timestamps. No personal data, no per-domain breakdown. Use for status pages, embedded usage badges, or tr...
AI agents call get_stats to retrieve information from Intodns without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries aggregate public statistics without creating, modifying, deleting, or executing any operations. The read-only nature, public data source, and explicit statement that it returns only counters and timestamps with no sensitive or per-domain information places it firmly in the Read category with minimal blast radius.
From the tool's definition Tool description explicitly states 'Read-only fetch of public IntoDNS.ai usage counters' with 'no personal data, no per-domain breakdown'. Returns aggregate statistics only via 'Single GET, no auth'. No mutations, side effects, or sensitive data access.
Attacks that exploit this kind of access
Read-only fetch of public IntoDNS.ai usage counters: total scans run, security checks performed, hall-of-fame entries, and rolling daily/weekly aggregates. Returns plain integer counters with timestamps. No personal data, no per-domain breakdown. Use for status pages, embedded usage badges, or trust signals in marketing copy; not a per-user dashboard. Single GET, no auth, ~100ms. It is categorised as a Read tool in the Intodns MCP Server, which means it retrieves data without modifying state.
Register the Intodns MCP server in PolicyLayer and add a rule for 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 Intodns. Nothing to install.
get_stats 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 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.
Set action: deny in the PolicyLayer policy for 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.
get_stats is provided by the Intodns MCP server (rosconl/intodns-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →