AI agents call get_electron_window_info to retrieve information from Electron without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about Electron app windows (structure, state, properties) and returns it as text output. There is no modification, deletion, code execution, or financial transaction involved. It is a straightforward read operation querying application metadata. The low severity reflects that window metadata disclosure poses minimal risk even if misused by an agent.
From the tool's definition Tool name is 'get_electron_window_info' and description states 'Electron app windows overview. Compact text output.' The 'get_' prefix and 'overview' language indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Electron app windows overview. Compact text output. It is categorised as a Read tool in the Electron MCP Server, which means it retrieves data without modifying state.
Register the Electron MCP server in PolicyLayer and add a rule for get_electron_window_info: 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 Electron. Nothing to install.
get_electron_window_info 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_electron_window_info 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_electron_window_info. 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_electron_window_info is provided by the Electron MCP server (ohah/electron-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 →