zte_run_page · Zte F680 MCP: Risk & Policy

WHAT IT DOES

What zte_run_page does on Zte F680

AI agents invoke zte_run_page to trigger actions in Zte F680. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why zte_run_page needs a policy

The tool name 'zte_run_page' uses the verb 'run', which indicates execution of code or commands on the router device. While the description is empty (lowering confidence), the context as a router management tool that already exposes write operations (add/delete port forwards) suggests this tool likely executes operations whose effects depend on arguments.

From the tool's definition Tool name 'zte_run_page' in context of a router management server suggests execution of commands or actions on the device.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zte_run_page Rate-limited

zte_run_page stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zte_run_page": {
      "limits": [
        {
          "counter": "zte_run_page_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Zte F680, so you can run agents against it safely.

FAQ

Questions about zte_run_page

What does the zte_run_page tool do? +

zte_run_page. It is categorised as a Execute tool in the Zte F680 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on zte_run_page? +

Register the Zte F680 MCP server in PolicyLayer and add a rule for zte_run_page: 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.

What risk level is zte_run_page? +

zte_run_page is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit zte_run_page? +

Yes. Add a rate_limit block to the zte_run_page 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.

How do I block zte_run_page completely? +

Set action: deny in the PolicyLayer policy for zte_run_page. 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.

What MCP server provides zte_run_page? +

zte_run_page 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.