search_dhcp_leases
AI agents call search_dhcp_leases to retrieve information from pfSense Enhanced MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Searching DHCP leases retrieves network lease information without modifying firewall state, configuration, or data. This is a passive information retrieval operation with minimal blast radius if misused—an AI agent could only over-query or request excessive data. The empty description slightly reduces confidence, but the tool name and server context clearly indicate a read operation.
From the tool's definition Tool name 'search_dhcp_leases' indicates a query/search operation on DHCP lease data. No description provided, but the naming pattern aligns with read-only lookups typical of search functions.
Attacks that exploit this kind of access
search_dhcp_leases. It is categorised as a Read tool in the pfSense Enhanced MCP Server MCP Server, which means it retrieves data without modifying state.
Register the pfSense Enhanced MCP Server MCP server in PolicyLayer and add a rule for search_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 pfSense Enhanced MCP Server. Nothing to install.
search_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 search_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 search_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.
search_dhcp_leases is provided by the pfSense Enhanced MCP Server MCP server (mmaxwellcb/pfsesen_mcp_2). 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 →