AI agents call zte_get_local_ip 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.
The 'get' prefix and naming convention align with Read-category operations. Retrieving the local IP address is a query that produces no side effects. The tool description is empty, which reduces confidence slightly, but the consistent naming pattern across sibling tools and the lack of modification verbs (add, delete, modify) support the Read classification. No blast radius for misuse.
From the tool's definition Tool name is 'zte_get_local_ip' with verb 'get', which indicates data retrieval. No description provided, but the name and context (sibling tools like zte_get_device_info, zte_get_dhcp_leases, zte_get_wan_status) strongly suggest this retrieves local IP…
Attacks that exploit this kind of access
zte_get_local_ip. 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_local_ip: 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_local_ip 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_local_ip 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_local_ip. 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_local_ip 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 →