Manage browser sessions: list, close, cleanup idle sessions, get status
AI agents invoke manage_browser_sessions to trigger actions in ZMCPTools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool performs active browser session management operations including closing and cleaning up sessions, which are external operations with side effects beyond simple reads. While 'list' and 'get status' are read operations, 'close' and 'cleanup idle sessions' terminate active browser sessions which cannot be easily undone (lost session state, cookies, active page contexts).
From the tool's definition Manage browser sessions: list, close, cleanup idle sessions, get status
Documented attack patterns abuse exactly the kind of access manage_browser_sessions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_browser_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"manage_browser_sessions": {
"limits": [
{
"counter": "manage_browser_sessions_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}manage_browser_sessions stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Manage browser sessions: list, close, cleanup idle sessions, get status. It is categorised as a Execute tool in the ZMCPTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for manage_browser_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 ZMCPTools. Nothing to install.
manage_browser_sessions is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the manage_browser_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 manage_browser_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.
manage_browser_sessions is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.