Evaluate the script
AI agents invoke evaluate-script to trigger actions in TgeBrowser 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.
Evaluating/executing scripts in a browser context can run arbitrary JavaScript, access browser state, exfiltrate data, interact with web pages, or perform any browser-based action. This is an Execute category tool with high severity due to the open-ended nature of arbitrary script execution in a live browser environment.
From the tool's definition Tool name 'evaluate-script' and description 'Evaluate the script' indicate execution of arbitrary script code within a browser environment.
Attacks that exploit this kind of access
Evaluate the script. It is categorised as a Execute tool in the TgeBrowser MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TgeBrowser MCP Server 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 TgeBrowser MCP Server. 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 TgeBrowser MCP Server MCP server (tuguang2025/tgebrowser-mcp-server). 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 →