Cierra todas las sesiones activas.
AI agents call close_all_sessions to permanently remove resources in MCP Selenium WebDriver — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Closing all active browser sessions is irreversible; any unsaved state, open tabs, or in-progress work across every session is permanently lost. This bulk termination action cannot be undone, making it Destructive. The blast radius is high because it affects all sessions at once, not just a single one.
From the tool's definition 'Cierra todas las sesiones activas' (Closes all active sessions) — terminates all running browser sessions simultaneously
Attacks that exploit this kind of access
Cierra todas las sesiones activas. It is categorised as a Destructive tool in the MCP Selenium WebDriver MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Selenium WebDriver MCP server in PolicyLayer and add a rule for close_all_sessions: 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 Selenium WebDriver. Nothing to install.
close_all_sessions is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the close_all_sessions 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_all_sessions. 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_all_sessions is provided by the MCP Selenium WebDriver MCP server (nixon-suarez/mcp-selenium-webdriver). 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 →