[LEGACY] List all browser sessions. Use manage_browser_sessions instead.
AI agents call list_browser_sessions to retrieve information from ZMCPTools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple enumeration/query operation to retrieve a list of existing browser sessions. It has no side effects, does not modify state, and does not execute actions. Listing sessions is a read-only operation with minimal security impact—the main risk would be information disclosure if the session list contains sensitive identifiers, but this is low severity for a browser session enumeration.
From the tool's definition Tool name 'list_browser_sessions' and description explicitly states it 'List[s] all browser sessions'. The verb 'list' is a read operation that retrieves information without modification. The tool is marked as [LEGACY], indicating it is deprecated.
Documented attack patterns abuse exactly the kind of access list_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 list_browser_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"list_browser_sessions": {}
}
}list_browser_sessions 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.
[LEGACY] List all browser sessions. Use manage_browser_sessions instead. It is categorised as a Read tool in the ZMCPTools MCP Server, which means it retrieves data without modifying state.
Register the ZMCPTools MCP server in PolicyLayer and add a rule for list_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.
list_browser_sessions 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 list_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 list_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.
list_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.