chrome_execute_script

Execute JavaScript code in the current page

SERVERChrome Feedback SOURCE2019-02-18/mcx

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/2019-02-18-mcx/chrome-execute-script.md

WHAT IT DOES

What chrome_execute_script does on Chrome Feedback

AI agents invoke chrome_execute_script to trigger actions in Chrome Feedback. 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.

RISK

Why chrome_execute_script is rated High

Executing JavaScript in a webpage context permits arbitrary DOM manipulation, data exfiltration, XSS-like injection, and interaction with page APIs. While not inherently destructive (no guarantee of permanent data loss) or financial, the capability to run code whose effects depend entirely on what script is supplied makes this an Execute-category risk.

From the tool's definition Tool description states 'Execute JavaScript code in the current page' — this directly runs code with arbitrary effects determined by the arguments passed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs chrome_execute_script safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Feedback, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chrome_execute_script, this is the rule to start with:

chrome_execute_script Rate-limited

chrome_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": {
    "chrome_execute_script": {
      "limits": [
        {
          "counter": "chrome_execute_script_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Feedback, apply this rule, and every chrome_execute_script call is checked against it from then on.

FAQ

Questions about chrome_execute_script

What does the chrome_execute_script tool do? +

Execute JavaScript code in the current page. It is categorised as a Execute tool in the Chrome Feedback MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on chrome_execute_script? +

Register the Chrome Feedback MCP server in PolicyLayer and add a rule for chrome_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 Chrome Feedback. Nothing to install.

What risk level is chrome_execute_script? +

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

Can I rate-limit chrome_execute_script? +

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

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

chrome_execute_script is provided by the Chrome Feedback MCP server (2019-02-18/mcx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Feedback, and thousands of servers like it.

This server

All 16 Chrome Feedback tools → High-risk tools on this server →

Across the catalogue

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server →load_script on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →