AI agents call pihole_get_status to retrieve information from Homelab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of Pi-hole DNS instances to determine their availability. It is a pure read operation with no side effects, no data modification, and no external execution. The blast radius of misuse is minimal—an agent could only obtain operational status information about network DNS infrastructure.
From the tool's definition Tool name 'pihole_get_status' and description 'Check which Pi-hole instances are online' indicate a query operation that retrieves status information without modifying any data or triggering actions.
Attacks that exploit this kind of access
Check which Pi-hole instances are online. It is categorised as a Read tool in the Homelab MCP Server, which means it retrieves data without modifying state.
Register the Homelab MCP server in PolicyLayer and add a rule for pihole_get_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 Homelab. Nothing to install.
pihole_get_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 pihole_get_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 pihole_get_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.
pihole_get_status is provided by the Homelab MCP server (myraffy/homelab-mcp). 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 →