evaluate_js · Chrome Profile MCP Server MCP: Risk & Policy

WHAT IT DOES

What evaluate_js does on Chrome Profile MCP Server

AI agents invoke evaluate_js to trigger actions in Chrome Profile 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 evaluate_js needs a policy

This tool runs arbitrary code (JavaScript) in the context of a real Chrome browser instance. Combined with the sibling tools showing real Google Chrome control via Chrome DevTools Protocol, misuse of this tool could allow an AI agent to exfiltrate cookies, credentials, and sensitive page data; manipulate page content; perform unauthorized actions (clicks, form submissions) on the user's behalf; or trigger malicious…

From the tool's definition Tool description explicitly states "Execute JavaScript code in the page context". JavaScript execution in a live Chrome instance enables arbitrary code execution with full access to the page's DOM, sensitive data, and browser APIs.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

evaluate_js Rate-limited

evaluate_js 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": {
    "evaluate_js": {
      "limits": [
        {
          "counter": "evaluate_js_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 Chrome Profile MCP Server, so you can run agents against it safely.

FAQ

Questions about evaluate_js

What does the evaluate_js tool do? +

Execute JavaScript code in the page context and return the result. It is categorised as a Execute tool in the Chrome Profile 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 evaluate_js? +

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

What risk level is evaluate_js? +

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

Can I rate-limit evaluate_js? +

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

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

evaluate_js is provided by the Chrome Profile MCP Server MCP server (nghiahsgs/vibe-mcp-chrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.