browser_navigate_back · Amazon MQ MCP Server MCP

WHAT IT DOES

What browser_navigate_back does on Amazon MQ MCP Server

AI agents invoke browser_navigate_back to trigger actions in Amazon MQ 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.

WHY IT NEEDS A POLICY

Why browser_navigate_back needs a policy

Browser navigation (back button) executes an operation in an external system whose effects depend on browsing context. Without a description, confidence is moderate. The tool appears contextually misplaced on an Amazon MQ server (which manages message brokers), suggesting it may be a copy-paste error or part of a broader toolset.

From the tool's definition Tool named 'browser_navigate_back' with empty description. The name indicates a browser navigation action, which is an Execute operation that triggers an external system (browser) to perform a state-changing action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_navigate_back Rate-limited

browser_navigate_back 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": {
    "browser_navigate_back": {
      "limits": [
        {
          "counter": "browser_navigate_back_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 Amazon MQ MCP Server, so you can run agents against it safely.

FAQ

Questions about browser_navigate_back

What does the browser_navigate_back tool do? +

browser_navigate_back. It is categorised as a Execute tool in the Amazon MQ 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_back? +

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

What risk level is browser_navigate_back? +

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

Can I rate-limit browser_navigate_back? +

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

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

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