pihole_get_stats

// WHEN AI AGENTS USE THIS TOOL

AI agents call pihole_get_stats to retrieve information from Mcp Pihole without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON PIHOLE_GET_STATS

Even though pihole_get_stats only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-aplaceforallmystuff-mcp-pihole.yaml

tools:
  pihole_get_stats:
    rules:
      - action: allow

See the full Mcp Pihole policy for all 16 tools.

// DETAILS

Tool Name pihole_get_stats

Category Read

MCP Server Mcp Pihole MCP Server

Risk Level Low

// MORE MCP PIHOLE TOOLS

Destructive pihole_flush_cache Destructive pihole_remove_from_blacklist Destructive pihole_remove_from_whitelist Execute pihole_update_gravity Write pihole_add_to_blacklist Write pihole_add_to_whitelist Write pihole_disable_blocking Write pihole_enable_blocking

View all 16 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like pihole_get_stats have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the pihole_get_stats tool do? +

Get comprehensive Pi-hole statistics. It is categorised as a Read tool in the Mcp Pihole MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pihole_get_stats? +

Add a rule in your Intercept YAML policy under the tools section for pihole_get_stats. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Pihole MCP server.

What risk level is pihole_get_stats? +

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

Can I rate-limit pihole_get_stats? +

Yes. Add a rate_limit block to the pihole_get_stats rule in your Intercept 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 pihole_get_stats completely? +

Set action: deny in the Intercept policy for pihole_get_stats. 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 pihole_get_stats? +

pihole_get_stats is provided by the Mcp Pihole MCP server (mcp-pihole-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Mcp Pihole