cleanup_idle_sessions

THE RISK

Critical Risk

Why cleanup_idle_sessions needs a policy

Closing browser sessions cannot be undone; any unsaved session state, cookies, or in-progress automation work is permanently lost. The tool automatically acts on idle sessions, which increases the blast radius if misconfigured. Classified as Destructive due to irreversibility, medium severity since it affects browser sessions rather than persistent data.

From the tool's definition 'Automatically close idle browser sessions' — closing/terminating sessions is irreversible; the session state is lost once closed

Documented attack patterns abuse exactly the kind of access cleanup_idle_sessions gives an agent:

POLICY

How to control cleanup_idle_sessions

PolicyLayer is an MCP gateway — it sits between your AI agents and RunAutomation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cleanup_idle_sessions:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "cleanup_idle_sessions"
  ]
}

cleanup_idle_sessions disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register RunAutomation MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More RunAutomation MCP Server tools

Destructive clear_codegen_session Clear a code generation session without generating a test Destructive close_browser_session Close a specific browser session and cleanup all resources including browser instance, pag Destructive playwright_close Close the browser and release all resources Execute playwright_delete Perform an HTTP DELETE request Execute playwright_batch_ai_visual_compare Run batch AI visual comparisons across multiple pages Execute playwright_emulate_device Emulate a mobile device with specific viewport, user agent, and capabilities. Supports all Execute playwright_evaluate Execute JavaScript in the browser console Execute playwright_expect_response Ask Playwright to start waiting for a HTTP response. This tool initiates the wait operatio

All 91 RunAutomation MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in RunAutomation MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cleanup_idle_sessions

What does the cleanup_idle_sessions tool do? +

Automatically close idle browser sessions that haven. It is categorised as a Destructive tool in the RunAutomation MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cleanup_idle_sessions? +

Register the RunAutomation MCP Server MCP server in PolicyLayer and add a rule for cleanup_idle_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 RunAutomation MCP Server. Nothing to install.

What risk level is cleanup_idle_sessions? +

cleanup_idle_sessions is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cleanup_idle_sessions? +

Yes. Add a rate_limit block to the cleanup_idle_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.

How do I block cleanup_idle_sessions completely? +

Set action: deny in the PolicyLayer policy for cleanup_idle_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.

What MCP server provides cleanup_idle_sessions? +

cleanup_idle_sessions is provided by the RunAutomation MCP Server MCP server (tayyabakmal1/runautomation-mcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every RunAutomation MCP Server tool call.

Start from RunAutomation MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →