Get detailed DNS cache information with parsed entries
AI agents call dns_cache_detailed to retrieve information from Mcp Windows without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing DNS cache state without modifying, executing, or deleting anything. It is purely informational with no side effects or ability to alter system state. Low severity because DNS cache inspection poses minimal security risk—an AI reading cached DNS entries cannot directly harm the system.
From the tool's definition Tool name 'dns_cache_detailed' and description 'Get detailed DNS cache information with parsed entries' indicate data retrieval only. The verb 'Get' and lack of modification language (no create/update/delete/execute) confirm read-only behavior.
Documented attack patterns abuse exactly the kind of access dns_cache_detailed gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for dns_cache_detailed:
{
"version": "1",
"default": "deny",
"tools": {
"dns_cache_detailed": {}
}
}dns_cache_detailed is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get detailed DNS cache information with parsed entries. It is categorised as a Read tool in the Mcp Windows MCP Server, which means it retrieves data without modifying state.
Register the Mcp Windows MCP server in PolicyLayer and add a rule for dns_cache_detailed: 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 Mcp Windows. Nothing to install.
dns_cache_detailed 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 dns_cache_detailed 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 dns_cache_detailed. 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.
dns_cache_detailed is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.