nav_forward · Ruyipage MCP: Risk & Policy

WHAT IT DOES

What nav_forward does on Ruyipage

AI agents invoke nav_forward to trigger actions in Ruyipage. 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 nav_forward needs a policy

This tool triggers a browser navigation action (history forward), which is an external browser operation with side effects. It changes the browser state and may trigger page loads, scripts, or network requests. It falls under Execute as it controls browser behavior rather than simply reading data.

From the tool's definition Go forward in browser history

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

nav_forward Rate-limited

nav_forward 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": {
    "nav_forward": {
      "limits": [
        {
          "counter": "nav_forward_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 Ruyipage, so you can run agents against it safely.

FAQ

Questions about nav_forward

What does the nav_forward tool do? +

Go forward in browser history. It is categorised as a Execute tool in the Ruyipage MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on nav_forward? +

Register the Ruyipage MCP server in PolicyLayer and add a rule for nav_forward: 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 Ruyipage. Nothing to install.

What risk level is nav_forward? +

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

Can I rate-limit nav_forward? +

Yes. Add a rate_limit block to the nav_forward 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 nav_forward completely? +

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

nav_forward is provided by the Ruyipage MCP server (neverl805/ruyipage_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.