check_pihole
Check Pi-hole DNS ad blocker status via the admin API. Returns enabled, blocking status, DNS queries today, and ads blocked. api_token: Pi-hole API token from Settings > API/Web interface (optional — some stats available without auth). Default port 80.
This record as markdown: /tools/aaronckj-mcp-nettools/check-pihole.md
What check_pihole does on Mcp Nettools
AI agents call check_pihole to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_pihole is rated Low
This tool queries the status and statistics of a Pi-hole DNS ad blocker via its admin API. It retrieves read-only data (enabled/blocking status, query counts, blocked ad counts) without creating, modifying, deleting, or executing operations. The optional API token indicates authentication for information access, not authorization for mutations or side effects.
From the tool's definition Tool description states it 'Returns enabled, blocking status, DNS queries today, and ads blocked' — all query/retrieval operations with 'api_token' described as optional. No modification, deletion, or execution of external commands.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs check_pihole safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_pihole, this is the rule to start with:
check_pihole is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_pihole call is checked against it from then on.
Questions about check_pihole
Check Pi-hole DNS ad blocker status via the admin API. Returns enabled, blocking status, DNS queries today, and ads blocked. api_token: Pi-hole API token from Settings > API/Web interface (optional — some stats available without auth). Default port 80. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.
Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_pihole: 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 Nettools. Nothing to install.
check_pihole 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 check_pihole 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 check_pihole. 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.
check_pihole is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Nettools, and thousands of servers like it.
This server
Across the catalogue