switch_browser · InSite MCP: Risk & Policy

WHAT IT DOES

What switch_browser does on InSite

AI agents invoke switch_browser to trigger actions in InSite. 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 switch_browser needs a policy

Switching the active browser engine triggers an external operation that changes the runtime environment for subsequent browser automation actions. It is not a simple read, write, or delete, but an operational state change that affects how further commands are executed.

From the tool's definition Switch to a different browser engine (chromium, firefox, webkit)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

switch_browser Rate-limited

switch_browser 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": {
    "switch_browser": {
      "limits": [
        {
          "counter": "switch_browser_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 InSite, so you can run agents against it safely.

FAQ

Questions about switch_browser

What does the switch_browser tool do? +

Switch to a different browser engine (chromium, firefox, webkit). It is categorised as a Execute tool in the InSite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on switch_browser? +

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

What risk level is switch_browser? +

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

Can I rate-limit switch_browser? +

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

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

switch_browser is provided by the InSite MCP server (jowharshamshiri/insite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.