Get recent DNS queries.
AI agents call get_queries to retrieve information from Mcp Pihole without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical DNS query data from Pi-hole for diagnostic or analysis purposes. It has no side effects, does not modify any configuration or data, and does not execute any operations. Retrieving logs or query history is a read-only operation with minimal security risk—the data returned reflects what has already occurred and cannot be altered by this tool's invocation.
From the tool's definition Tool name 'get_queries' and description 'Get recent DNS queries' indicate a retrieval operation with no modification, deletion, or execution of external commands. The verb 'Get' is a standard read operation.
Attacks that exploit this kind of access
Get recent DNS queries. It is categorised as a Read tool in the Mcp Pihole MCP Server, which means it retrieves data without modifying state.
Register the Mcp Pihole MCP server in PolicyLayer and add a rule for get_queries: 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 Pihole. Nothing to install.
get_queries 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_queries 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_queries. 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_queries is provided by the Mcp Pihole MCP server (obrien-matthew/mcp-pihole). 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 →