stop_browser_session · AWS IoT SiteWise MCP Server MCP

WHAT IT DOES

What stop_browser_session does on AWS IoT SiteWise MCP Server

AI agents invoke stop_browser_session to trigger actions in AWS IoT SiteWise 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 stop_browser_session needs a policy

Stopping a browser session is an active operation that triggers external effects (session termination, potential resource cleanup, state changes in monitored systems). While not data-destructive, it executes a command with side effects dependent on which session is targeted.

From the tool's definition Tool name 'stop_browser_session' indicates termination of an active browser session; sibling tools include browser automation patterns (analyze_canary_failures, analyze_cdk_project) suggesting this server manages browser-based operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_browser_session Rate-limited

stop_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": {
    "stop_browser_session": {
      "limits": [
        {
          "counter": "stop_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 AWS IoT SiteWise MCP Server, so you can run agents against it safely.

FAQ

Questions about stop_browser_session

What does the stop_browser_session tool do? +

stop_browser_session. It is categorised as a Execute tool in the AWS IoT SiteWise 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 stop_browser_session? +

Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for stop_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 AWS IoT SiteWise MCP Server. Nothing to install.

What risk level is stop_browser_session? +

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

Can I rate-limit stop_browser_session? +

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

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

stop_browser_session is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.