browser_session-list

List active browser sessions Use when native WebFetch is wrong because you need real browser automation — JS-heavy SPA scraping, login flows with cookie reuse, replay against DOM-drifted versions, AIDefence PII gating before content reaches Claude. For static HTML pages, native WebFetch is faster...

SERVERRuflo SOURCEruvnet/ruflo

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ruflo/browser-session-list.md

WHAT IT DOES

What browser_session-list does on Ruflo

AI agents call browser_session-list to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why browser_session-list is rated Low

This tool enumerates existing browser sessions, a read-only enumeration action. Although browser automation is mentioned in the description as a use case (JS-heavy SPA scraping, login flows), the specific tool merely lists sessions rather than creating, modifying, executing actions within them, or deleting them. The highest-severity sibling tool is 'agent_terminate' (destructive).

From the tool's definition Tool name is 'browser_session-list' with verb 'List' and description states 'List active browser sessions' — purely retrieves/queries state without modifying or executing operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_session-list safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_session-list, this is the rule to start with:

browser_session-list Allowed

browser_session-list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_session-list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every browser_session-list call is checked against it from then on.

FAQ

Questions about browser_session-list

What does the browser_session-list tool do? +

How do I enforce a policy on browser_session-list? +

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

What risk level is browser_session-list? +

browser_session-list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser_session-list? +

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

How do I block browser_session-list completely? +

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

What MCP server provides browser_session-list? +

browser_session-list is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ruflo, and thousands of servers like it.

This server

All 496 Ruflo tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →