nav_get · Ruyipage MCP: Risk & Policy

WHAT IT DOES

What nav_get does on Ruyipage

AI agents invoke nav_get 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_get needs a policy

Navigating to a URL is an external browser operation that can trigger page loads, execute JavaScript on target pages, submit forms via URL parameters, or access sensitive resources. It goes beyond a simple read because it causes the browser to perform an action in the real world. Misuse could lead to visiting malicious sites, exfiltrating data via URL, or triggering unintended web actions.

From the tool's definition Navigate to a URL — triggers browser navigation, an external operation with side effects depending on the URL argument

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

nav_get Rate-limited

nav_get 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_get": {
      "limits": [
        {
          "counter": "nav_get_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_get

What does the nav_get tool do? +

Navigate to a URL. 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_get? +

Register the Ruyipage MCP server in PolicyLayer and add a rule for nav_get: 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_get? +

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

Can I rate-limit nav_get? +

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

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

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