browser_execute_script · MCP Browser Screenshot Server MCP

WHAT IT DOES

What browser_execute_script does on MCP Browser Screenshot Server

AI agents invoke browser_execute_script to trigger actions in MCP Browser Screenshot 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_execute_script needs a policy

This tool allows arbitrary code execution in a browser context controlled by an AI agent. An agent could use it to exfiltrate data from visited pages, redirect to malicious sites, keylog user input, inject malware, perform unauthorized API calls, or trigger unintended actions on web services. The impact depends entirely on what JavaScript the agent chooses to execute.

From the tool's definition Tool name: 'browser_execute_script'; Description: 'Execute JavaScript in the browser context'. The tool explicitly permits arbitrary JavaScript execution within an automated browser session.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

browser_execute_script Rate-limited

browser_execute_script 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_execute_script": {
      "limits": [
        {
          "counter": "browser_execute_script_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 MCP Browser Screenshot Server, so you can run agents against it safely.

FAQ

Questions about browser_execute_script

What does the browser_execute_script tool do? +

Execute JavaScript in the browser context. It is categorised as a Execute tool in the MCP Browser Screenshot 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_execute_script? +

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

What risk level is browser_execute_script? +

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

Can I rate-limit browser_execute_script? +

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

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

browser_execute_script is provided by the MCP Browser Screenshot Server MCP server (seabassgonzalez/mcp-browser-screenshot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.