execute_js · WebControl MCP: Risk & Policy

WHAT IT DOES

What execute_js does on WebControl

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

This tool allows arbitrary code execution within a browser session. While the description says it 'returns updated page content' (suggesting read-like behavior), the primary capability is executing JavaScript, which is inherently an Execute category action.

From the tool's definition Tool name is 'execute_js' and description states 'Execute JavaScript on the current page.' JavaScript execution in a browser context can interact with page state, trigger side effects, call APIs, modify the DOM, access cookies/storage, and perform…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_js Rate-limited

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

FAQ

Questions about execute_js

What does the execute_js tool do? +

Execute JavaScript on the current page. Returns updated page content. It is categorised as a Execute tool in the WebControl MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_js? +

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

What risk level is execute_js? +

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

Can I rate-limit execute_js? +

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

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

execute_js is provided by the WebControl MCP server (matansht/webcontrol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.