executes JavaScript in the browser and returns the result. Use for advanced interactions not covered by other tools (e.g., drag and drop, scrolling, reading computed styles, manipulating the DOM directly). Also useful for batch-reading multiple element values/states in a single call instead of mu...
AI agents invoke execute_script to trigger actions in Mcp Selenium. 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.
This tool executes arbitrary code (JavaScript) in a browser context, which can trigger side effects including navigation, form submission, data exfiltration, session manipulation, and DOM modifications. While it doesn't itself delete data or move money, it has the capability to trigger such actions through JavaScript execution.
From the tool's definition Tool description explicitly states it "executes JavaScript in the browser" and mentions capabilities like "manipulating the DOM directly", "drag and drop", "scrolling", and batch operations.
Attacks that exploit this kind of access
executes JavaScript in the browser and returns the result. Use for advanced interactions not covered by other tools (e.g., drag and drop, scrolling, reading computed styles, manipulating the DOM directly). Also useful for batch-reading multiple element values/states in a single call instead of multiple get_element_attribute calls. It is categorised as a Execute tool in the Mcp Selenium MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Selenium MCP server in PolicyLayer and add a rule for 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 Selenium. Nothing to install.
execute_script is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
execute_script is provided by the Mcp Selenium MCP server (@angiejones/mcp-selenium). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →