list_query_history

THE RISK

Low Risk

Why list_query_history needs a policy

This tool retrieves and queries historical DNS query data from Pi-hole for analysis and reporting purposes. While it accesses query history (which could reveal browsing patterns), it performs no writes, deletions, or external operations. The data retrieved is read-only activity analytics.

From the tool's definition Tool name 'list_query_history' and description 'Get activity graph data for Pi-hole queries over time' indicate data retrieval without modification.

Documented attack patterns abuse exactly the kind of access list_query_history gives an agent:

POLICY

How to control list_query_history

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_history:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_query_history": {}
  }
}

list_query_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Pi-hole MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Pi-hole MCP Server tools

Destructive remove_local_a_record Remove a local A record from Pi-hole with confirmation token Destructive remove_local_cname_record Remove a local CNAME record from Pi-hole with confirmation token Write add_local_a_record Add a local A record to Pi-hole Write add_local_cname_record Add a local CNAME record to Pi-hole Read list_local_dns List local A and CNAME records from Pi-hole Read list_queries Fetch recent DNS query history with filtering options Read list_query_suggestions Get query filter suggestions for Pi-hole query data

All 8 Pi-hole MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_query_history

What does the list_query_history tool do? +

Get activity graph data for Pi-hole queries over time. It is categorised as a Read tool in the Pi-hole MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_query_history? +

Register the Pi-hole MCP Server MCP server in PolicyLayer and add a rule for list_query_history: 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.

What risk level is list_query_history? +

list_query_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_query_history? +

Yes. Add a rate_limit block to the list_query_history 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.

How do I block list_query_history completely? +

Set action: deny in the PolicyLayer policy for list_query_history. 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.

What MCP server provides list_query_history? +

list_query_history 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.

Enforce policy on every Pi-hole MCP Server tool call.

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.

CHECK YOUR STACK →