Get current DNS blocking status.
AI agents call get_blocking_status to retrieve information from Mcp Pihole without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and reports the current state of DNS blocking configuration. It queries data (blocking status) without creating, modifying, deleting, or executing any operations. The verb 'Get' and absence of any mutative operations confirm it is a Read category tool with low severity—accessing status information poses minimal risk even if called inappropriately by an agent.
From the tool's definition Tool name 'get_blocking_status' combined with description 'Get current DNS blocking status' indicates retrieval of status information with no side effects.
Attacks that exploit this kind of access
Get current DNS blocking status. It is categorised as a Read tool in the Mcp Pihole MCP Server, which means it retrieves data without modifying state.
Register the Mcp Pihole MCP server in PolicyLayer and add a rule for get_blocking_status: 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 Pihole. Nothing to install.
get_blocking_status 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 get_blocking_status 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 get_blocking_status. 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.
get_blocking_status is provided by the Mcp Pihole MCP server (obrien-matthew/mcp-pihole). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →