Fetch recent DNS query history with filtering options
AI agents call list_queries to retrieve information from Pi-hole 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 and queries DNS query history data. It has no side effects—it does not create, modify, delete, execute code, or commit financial transactions. The filtering options are parameters for querying, not for modifying underlying data. This is a straightforward read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'list_queries' and description states 'Fetch recent DNS query history with filtering options'. The verb 'fetch' and noun 'history' indicate data retrieval without modification.
Documented attack patterns abuse exactly the kind of access list_queries gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pi-hole MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_queries:
{
"version": "1",
"default": "deny",
"tools": {
"list_queries": {}
}
}list_queries 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.
Fetch recent DNS query history with filtering options. It is categorised as a Read tool in the Pi-hole MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pi-hole MCP Server MCP server in PolicyLayer and add a rule for list_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 Pi-hole MCP Server. Nothing to install.
list_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 list_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 list_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.
list_queries is provided by the Pi-hole MCP Server MCP server (sbarbett/pihole-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pi-hole MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Pi-hole MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.