Get current DHCP leases.
AI agents call get_dhcp_leases 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 retrieves information about current DHCP leases—a passive data query operation. It does not modify, delete, or execute anything. While the information could theoretically be sensitive (IP addresses, device identities), the tool itself only reads and returns data. Misuse would cause information disclosure but not system damage or irreversible changes.
From the tool's definition Tool name 'get_dhcp_leases' and description 'Get current DHCP leases' indicate a query/retrieval operation with no side effects. The verb 'Get' is explicitly a read operation that retrieves existing data about DHCP lease states.
Attacks that exploit this kind of access
Get current DHCP leases. 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_dhcp_leases: 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_dhcp_leases 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_dhcp_leases 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_dhcp_leases. 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_dhcp_leases 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 →