AI agents use zte_open_port to create or update resources in Zte F680 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zte F680 environment.
This tool creates or modifies network access rules on a router, enabling or exposing ports to external traffic. While reversible (can be undone by closing the port), it has high blast radius: an AI agent could expose internal services to the internet, create security vulnerabilities, or enable unauthorized access.
From the tool's definition Tool name 'zte_open_port' indicates network configuration modification. Sibling tools include 'zte_add_port_forward' and 'zte_delete_port_forward', establishing that this server manages port forwarding rules.
Attacks that exploit this kind of access
zte_open_port. It is categorised as a Write tool in the Zte F680 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zte F680 MCP server in PolicyLayer and add a rule for zte_open_port: 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_open_port is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the zte_open_port 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_open_port. 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_open_port 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 →