AI agents call zte_get_dhcp_leases to retrieve information from Zte F680 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves DHCP lease data from the router without modifying, deleting, or executing any operations. It has no side effects—it only returns information about connected devices. This is a classic Read operation with low risk unless the queried information itself is highly sensitive, but disclosure of local network DHCP leases is a standard network query with minimal blast radius.
From the tool's definition Tool name 'zte_get_dhcp_leases' and description 'Lista los dispositivos conectados al router: IP, MAC, hostname' indicate retrieval of DHCP lease information (IP addresses, MAC addresses, hostnames of connected devices).
Attacks that exploit this kind of access
Lista los dispositivos conectados al router: IP, MAC, hostname,. It is categorised as a Read tool in the Zte F680 MCP Server, which means it retrieves data without modifying state.
Register the Zte F680 MCP server in PolicyLayer and add a rule for zte_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 Zte F680. Nothing to install.
zte_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 zte_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 zte_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.
zte_get_dhcp_leases is provided by the Zte F680 MCP server (picaresco/mcp-zte-f680). 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 →