List all active browser sessions with their URLs and status. Useful for managing multiple test scenarios.
AI agents call session_list to retrieve information from Firefox MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about existing browser sessions. It performs a read-only query of session state without modifying, executing, or destroying anything. The blast radius is minimal—an attacker could learn which tabs/sessions are open and their URLs, but cannot execute code, modify data, or access sensitive content beyond visible session metadata.
From the tool's definition Tool description states 'List all active browser sessions with their URLs and status' — a pure retrieval operation with no side effects. No modification, execution, or deletion occurs.
Documented attack patterns abuse exactly the kind of access session_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Firefox MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for session_list:
{
"version": "1",
"default": "deny",
"tools": {
"session_list": {}
}
} session_list 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.
List all active browser sessions with their URLs and status. Useful for managing multiple test scenarios. It is categorised as a Read tool in the Firefox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Firefox MCP Server MCP server in PolicyLayer and add a rule for session_list: 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 Firefox MCP Server. Nothing to install.
session_list 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 session_list 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 session_list. 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.
session_list is provided by the Firefox MCP Server MCP server (jediluke/firefox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Firefox MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 Firefox MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.