Get BrowserWindow object for a specific window
AI agents call electron_browser_window to retrieve information from Playwright MCP with Electron Support without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation on an existing window object. While it provides access to window state that could theoretically be used as input to other tools that modify or execute code, the tool itself only queries and returns data. The sibling tools (browser_click, browser_navigate, browser_console_messages, etc.) handle actual interactions and state changes.
From the tool's definition Tool name and description indicate it retrieves or queries a BrowserWindow object for inspection. The description uses 'Get', which is a read operation with no side effects. It provides access to window metadata/state, not modification or execution.
Documented attack patterns abuse exactly the kind of access electron_browser_window gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright MCP with Electron Support, and nothing reaches the server without passing your rules. This is the rule we recommend for electron_browser_window:
{
"version": "1",
"default": "deny",
"tools": {
"electron_browser_window": {}
}
}electron_browser_window is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get BrowserWindow object for a specific window. It is categorised as a Read tool in the Playwright MCP with Electron Support MCP Server, which means it retrieves data without modifying state.
Register the Playwright MCP with Electron Support MCP server in PolicyLayer and add a rule for electron_browser_window: 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 Playwright MCP with Electron Support. Nothing to install.
electron_browser_window 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 electron_browser_window 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 electron_browser_window. 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.
electron_browser_window is provided by the Playwright MCP with Electron Support MCP server (robertn702/playwright-mcp-electron). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright MCP with Electron Support, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Playwright MCP with Electron Support tools catalogued and risk-classified — across an index of 43,000+ MCP servers.