list_globals
Lists all global variables on the window object, excluding built-in browser APIs. Useful for finding custom variables, configs, tokens, and encryption functions.
This record as markdown: /tools/1600822305-js-reverse-mcp/list-globals.md
What list_globals does on Js Reverse
AI agents call list_globals to retrieve information from Js Reverse without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_globals is rated Low
This tool retrieves data (global variables) without side effects, placing it in the Read category. However, severity is high because the data it exposes—authentication tokens, encryption functions, and configuration secrets—could enable further attacks if an AI agent misuses this tool to exfiltrate sensitive information.
From the tool's definition Tool 'lists all global variables on the window object' - a query operation with no modification capability. Description emphasizes discovery of 'custom variables, configs, tokens, and encryption functions'.
Attacks that exploit this kind of access
The rule that runs list_globals safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Js Reverse, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_globals, this is the rule to start with:
list_globals is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Js Reverse, apply this rule, and every list_globals call is checked against it from then on.
Questions about list_globals
Lists all global variables on the window object, excluding built-in browser APIs. Useful for finding custom variables, configs, tokens, and encryption functions. It is categorised as a Read tool in the Js Reverse MCP Server, which means it retrieves data without modifying state.
Register the Js Reverse MCP server in PolicyLayer and add a rule for list_globals: 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 Js Reverse. Nothing to install.
list_globals 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 list_globals 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 list_globals. 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.
list_globals is provided by the Js Reverse MCP server (1600822305/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Js Reverse, and thousands of servers like it.
This server
Across the catalogue