Evaluate JavaScript expressions in the context of a call frame
AI agents invoke evaluate-expression to trigger actions in Debugger 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.
This tool executes arbitrary JavaScript code within a debugging call frame context. An AI agent could misuse this to run malicious scripts, access sensitive application state, exfiltrate data, or cause unintended side effects in the running application. Executing arbitrary code in a live browser/application context is a high-severity Execute-category action.
From the tool's definition 'Evaluate JavaScript expressions in the context of a call frame'
Attacks that exploit this kind of access
Evaluate JavaScript expressions in the context of a call frame. It is categorised as a Execute tool in the Debugger MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Debugger MCP Server MCP server in PolicyLayer and add a rule for evaluate-expression: 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 Debugger MCP Server. Nothing to install.
evaluate-expression 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-expression 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-expression. 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-expression is provided by the Debugger MCP Server MCP server (phoenixrr2113/debugger-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 →