16 tools. 8 can modify or destroy data without limits.
3 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (pihole_flush_cache, pihole_remove_from_blacklist, pihole_remove_from_whitelist) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (pihole_add_to_blacklist, pihole_add_to_whitelist, pihole_disable_blocking) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (pihole_update_gravity) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Mcp Pihole. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @mcp-pihole-server pihole_flush_cache:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
pihole_add_to_blacklist:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
pihole_get_blacklist:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Mcp Pihole server exposes 3 destructive tools including pihole_flush_cache, pihole_remove_from_blacklist, pihole_remove_from_whitelist. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Mcp Pihole server has 4 write tools including pihole_add_to_blacklist, pihole_add_to_whitelist, pihole_disable_blocking. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
16 tools across 4 categories: Destructive, Execute, Read, Write. 8 are read-only. 8 can modify, create, or delete data.
One line change. Instead of running the Mcp Pihole server directly, prefix it with Intercept: intercept -c io-github-aplaceforallmystuff-mcp-pihole.yaml -- npx -y @mcp-pihole-server. Download a pre-built policy from policylayer.com/policies/io-github-aplaceforallmystuff-mcp-pihole and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init