Get query filter suggestions for Pi-hole query data
AI agents call list_query_suggestions 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 returns query filter suggestions—a read-only operation with no side effects. It does not create, modify, delete, execute code, or involve financial transactions. The low severity reflects minimal blast radius: misuse would only surface suggestions based on existing data, posing no risk to system integrity or data loss.
From the tool's definition Tool name 'list_query_suggestions' combined with description 'Get query filter suggestions for Pi-hole query data' indicates a retrieval operation that provides suggestions/metadata for filtering existing query data without modifying, deleting, or executing…
Documented attack patterns abuse exactly the kind of access list_query_suggestions 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_query_suggestions:
{
"version": "1",
"default": "deny",
"tools": {
"list_query_suggestions": {}
}
} list_query_suggestions 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 query filter suggestions for Pi-hole query data. 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_query_suggestions: 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_query_suggestions 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_query_suggestions 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_query_suggestions. 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_query_suggestions 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.