navigate_to_page · MCP Browser Text Reader MCP

WHAT IT DOES

What navigate_to_page does on MCP Browser Text Reader

AI agents invoke navigate_to_page to trigger actions in MCP Browser Text Reader. 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 navigate_to_page needs a policy

Navigation is an Execute action because it triggers external browser operations whose effects depend on the URL argument. While read-only in isolation, navigating to arbitrary URLs controlled by an AI agent creates severe risk: the browser will execute JavaScript, load remote content, and potentially trigger drive-by downloads or credential theft.

From the tool's definition Tool navigates to arbitrary URLs by controlling a real Chrome browser. Description states it 'Controls a real Chrome browser to navigate web pages' and this tool performs that navigation action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

navigate_to_page Rate-limited

navigate_to_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": {
    "navigate_to_page": {
      "limits": [
        {
          "counter": "navigate_to_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 MCP Browser Text Reader, so you can run agents against it safely.

FAQ

Questions about navigate_to_page

What does the navigate_to_page tool do? +

导航到指定URL. It is categorised as a Execute tool in the MCP Browser Text Reader MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on navigate_to_page? +

Register the MCP Browser Text Reader MCP server in PolicyLayer and add a rule for navigate_to_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 MCP Browser Text Reader. Nothing to install.

What risk level is navigate_to_page? +

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

Can I rate-limit navigate_to_page? +

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

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

navigate_to_page is provided by the MCP Browser Text Reader MCP server (tikous/mymcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.