get_doh_servers
AI agents call get_doh_servers to retrieve information from DoH MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about available DNS over HTTPS servers—a pure read operation with no side effects. The absence of a description lowers confidence slightly, but the naming convention and sibling tools (dns_lookup, dns_debug, dns_record_types) all suggest informational/query operations rather than mutations.
From the tool's definition Tool name 'get_doh_servers' indicates retrieval of DNS server information. Server description emphasizes 'query capabilities' and 'resolution results', which are read-only operations.
Attacks that exploit this kind of access
get_doh_servers. It is categorised as a Read tool in the DoH MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DoH MCP Server MCP server in PolicyLayer and add a rule for get_doh_servers: 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 DoH MCP Server. Nothing to install.
get_doh_servers 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_doh_servers 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_doh_servers. 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_doh_servers is provided by the DoH MCP Server MCP server (randark-jmt/doh-mcp). 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 →