Read-only health probe for the IntoDNS.ai backend itself (not a target domain). Returns API uptime, Redis/cache status, AI runtime availability (whether explain_issue and generate_dns_fix are reachable), and overall service status string. No domain parameter. Use as a pre-flight check before batc...
AI agents call get_health 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 is a diagnostic/monitoring tool that queries the health status of the IntoDNS.ai backend infrastructure. It has no side effects, makes no modifications, executes no code on external systems, and poses minimal risk even if called repeatedly or by a misbehaving agent. The 'read-only' designation and absence of any domain parameter or state-modifying actions clearly place it in the Read category with low severity.
From the tool's definition Tool description explicitly states 'Read-only health probe' and 'Returns API uptime, Redis/cache status, AI runtime availability, and overall service status string.' No parameters that affect any system state.
Attacks that exploit this kind of access
Read-only health probe for the IntoDNS.ai backend itself (not a target domain). Returns API uptime, Redis/cache status, AI runtime availability (whether explain_issue and generate_dns_fix are reachable), and overall service status string. No domain parameter. Use as a pre-flight check before batch jobs, or when diagnosing whether a downstream tool failure is the backend. 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_health: 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_health 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_health 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_health. 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_health 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 →