AI agents call list_local_dns 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 queries and retrieves DNS records without any side effects. It does not create, modify, delete, or execute operations. The sibling tools on the server include write operations (add_local_a_record, add_local_cname_record) and destructive operations (remove_local_a_record, remove_local_cname_record), but this tool is purely informational.
From the tool's definition Tool name 'list_local_dns' and description 'List local A and CNAME records from Pi-hole' indicate data retrieval with no modification or deletion. The verb 'list' is a classic Read operation.
Documented attack patterns abuse exactly the kind of access list_local_dns 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_local_dns:
{
"version": "1",
"default": "deny",
"tools": {
"list_local_dns": {}
}
}list_local_dns 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.
List local A and CNAME records from Pi-hole. 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_local_dns: 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_local_dns 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_local_dns 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_local_dns. 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_local_dns 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.