Evaluate a JavaScript function inside the currently selected page${cliArgs?.categoryExtensions ?
AI agents invoke evaluate_script to trigger actions in Opera DevTools MCP. 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.
Executing arbitrary JavaScript in a browser page can read sensitive data, modify DOM, exfiltrate credentials, interact with web APIs, or perform any action the page context allows. This is a classic Execute category with high severity due to broad blast radius.
From the tool's definition "Evaluate a JavaScript function inside the currently selected page" — directly executes arbitrary JavaScript in the browser page context
Attacks that exploit this kind of access
Evaluate a JavaScript function inside the currently selected page${cliArgs?.categoryExtensions ?. It is categorised as a Execute tool in the Opera DevTools MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Opera DevTools MCP server in PolicyLayer and add a rule for evaluate_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 Opera DevTools MCP. Nothing to install.
evaluate_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 evaluate_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 evaluate_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.
evaluate_script is provided by the Opera DevTools MCP server (operasoftware/opera-devtools-mcp). 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 →