AI agents use close_page to create or update resources in Electron — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Electron environment.
An AI agent can call close_page faster than any human can review — one bad instruction and it creates or modifies resources in Electron by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Close the tab/window for the given page ID (from list_pages). In CDP-only mode the app must expose a close-window API. It is categorised as a Write tool in the Electron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Electron MCP server in PolicyLayer and add a rule for close_page: 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.
close_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the close_page 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 close_page. 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.
close_page 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 →