Retrieves all variables in a specific scope.
AI agents call get_scope_variables to retrieve information from MCP JS Debugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves debugging information (variables in scope) without executing code, modifying state, or causing side effects. However, severity is elevated to 'medium' rather than 'low' because variable inspection during debugging can expose sensitive data (API keys, credentials, PII, business logic) that an AI agent could exfiltrate or log, creating a data exposure risk even though the tool itself performs no…
From the tool's definition Tool name 'get_scope_variables' and description 'Retrieves all variables in a specific scope' indicate a read-only operation that queries state without modifying it. The broader context of a debugging tool suite confirms this is inspection-focused.
Attacks that exploit this kind of access
Retrieves all variables in a specific scope. It is categorised as a Read tool in the MCP JS Debugger MCP Server, which means it retrieves data without modifying state.
Register the MCP JS Debugger MCP server in PolicyLayer and add a rule for get_scope_variables: 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 JS Debugger. Nothing to install.
get_scope_variables is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_scope_variables 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 get_scope_variables. 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.
get_scope_variables is provided by the MCP JS Debugger MCP server (johngrimes/mcp-js-debugger). 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 →