在浏览器中执行 JavaScript 代码并返回结果
AI agents invoke evaluate_javascript to trigger actions in MCP Browser Logger. 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 JavaScript in the browser context via Chrome DevTools Protocol. An AI agent could use it to perform any action the browser can, including data exfiltration, DOM manipulation, credential theft, navigation to malicious pages, or interacting with authenticated sessions — making it critical severity.
From the tool's definition 'evaluate_javascript' — description states '在浏览器中执行 JavaScript 代码并返回结果' (Execute JavaScript code in the browser and return results)
Attacks that exploit this kind of access
在浏览器中执行 JavaScript 代码并返回结果. It is categorised as a Execute tool in the MCP Browser Logger MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Browser Logger MCP server in PolicyLayer and add a rule for evaluate_javascript: 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 Browser Logger. Nothing to install.
evaluate_javascript 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_javascript 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_javascript. 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_javascript is provided by the MCP Browser Logger MCP server (tao-lionel/mcp-browser-logger). 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 →