browser_sessions

List all active browser sessions with their current URL, title, and age.

SERVERYaver SOURCEyaver-cli

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/io-github-kivanccakmak-yaver/browser-sessions.md

WHAT IT DOES

What browser_sessions does on Yaver

AI agents call browser_sessions to retrieve information from Yaver 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_sessions is rated Low

This tool queries and displays information about running browser sessions. The verb 'list' and the absence of any modification, deletion, or execution capability place it firmly in the Read category. The data retrieved is session metadata, not sensitive personal information beyond what is already observable by the user (who owns the device), so severity is low.

From the tool's definition Tool description states 'List all active browser sessions' — a retrieval operation with no side effects. Returns metadata (URL, title, age) about existing sessions without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_sessions safely

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

browser_sessions Allowed

browser_sessions 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_sessions": {}
  }
}

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

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

FAQ

Questions about browser_sessions

What does the browser_sessions tool do? +

List all active browser sessions with their current URL, title, and age. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_sessions? +

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

What risk level is browser_sessions? +

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

Can I rate-limit browser_sessions? +

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

How do I block browser_sessions completely? +

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

What MCP server provides browser_sessions? +

browser_sessions is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

browser_extract_text on Percepta MCP Server → The MCP Attack Database →

Guides

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