start_browser_session · Amazon MQ MCP Server MCP

WHAT IT DOES

What start_browser_session does on Amazon MQ MCP Server

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

Starting a browser session enables arbitrary web interactions including navigation, form submission, clicks, and data exfiltration. This is an Execute action with external side effects whose impact depends on subsequent agent instructions. Severity is high due to potential for phishing, credential theft, or unauthorized API calls through the browser.

From the tool's definition Tool name is 'start_browser_session' which initiates a browser automation session. While description is empty, the name clearly indicates browser control capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_browser_session Rate-limited

start_browser_session 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": {
    "start_browser_session": {
      "limits": [
        {
          "counter": "start_browser_session_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 start_browser_session

What does the start_browser_session tool do? +

start_browser_session. 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 start_browser_session? +

Register the Amazon MQ MCP Server MCP server in PolicyLayer and add a rule for start_browser_session: 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 start_browser_session? +

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

Can I rate-limit start_browser_session? +

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

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

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