Low Risk

browser_navigate_back

browser_navigate_back

How to control browser_navigate_back ↓

What browser_navigate_back does on Awslabs Amazon Sns Sqs

AI agents call browser_navigate_back as a supporting operation in Awslabs Amazon Sns Sqs workflows.

Low Risk

Why browser_navigate_back needs a policy

The description is empty and uninformative, making classification uncertain. The tool name suggests browser navigation (going back), which would typically be Execute category. However, given the mismatch with the SNS/SQS server context and lack of any description, confidence is very low. Classifying as Other due to insufficient information and apparent context mismatch.

From the tool's definition Tool name is 'browser_navigate_back' with empty description. The name suggests a browser navigation action (going back in browser history), which is an Execute-type action, but it seems out of place on an Amazon SNS/SQS MCP server.

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

How to control browser_navigate_back

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_navigate_back": {
      "limits": [
        {
          "counter": "browser_navigate_back_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

browser_navigate_back gets a rate cap, and everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Awslabs Amazon Sns Sqs — 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.
SET A RULE FOR THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about browser_navigate_back

What does the browser_navigate_back tool do? +

browser_navigate_back. It is categorised as a Other tool in the Awslabs Amazon Sns Sqs MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on browser_navigate_back? +

Register the Awslabs Amazon Sns Sqs 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 Awslabs Amazon Sns Sqs. Nothing to install.

What risk level is browser_navigate_back? +

browser_navigate_back is a Other tool with low risk. Read-only tools are generally safe to allow by default.

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 Awslabs Amazon Sns Sqs MCP server (awslabs.amazon-sns-sqs-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 Awslabs Amazon Sns Sqs tool call.

Start from Awslabs Amazon Sns Sqs, 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 Awslabs Amazon Sns Sqs 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.