High Risk →

browser_navigate

browser_navigate

How to control browser_navigate ↓

What browser_navigate does on Amazon Translate MCP Server

AI agents invoke browser_navigate to trigger actions in Amazon Translate MCP Server. 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.

High Risk

Why browser_navigate needs a policy

Browser navigation falls under Execute because it triggers external operations (HTTP requests, page loads, script execution) whose side effects depend on the arguments passed. The empty description lowers confidence slightly, but the tool name alone is sufficient to classify it as Execute rather than Read, since navigation can cause state changes on remote systems.

From the tool's definition Tool name 'browser_navigate' indicates browser automation/navigation capability. Description is empty, limiting direct evidence.

Documented attack patterns abuse exactly the kind of access browser_navigate gives an agent:

How to control browser_navigate

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon Translate MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_navigate:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_navigate": {
      "limits": [
        {
          "counter": "browser_navigate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Amazon Translate MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about browser_navigate

What does the browser_navigate tool do? +

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

How do I enforce a policy on browser_navigate? +

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

What risk level is browser_navigate? +

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

Can I rate-limit browser_navigate? +

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

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

browser_navigate is provided by the Amazon Translate MCP Server MCP server (awslabs.amazon-translate-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Translate MCP Server tool call.

Start from Amazon Translate MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

805 Amazon Translate MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.