session_list

List AI agent sessions that can be transferred to another machine. Shows task ID, agent type, title, status, and whether the session is resumable.

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/session-list.md

WHAT IT DOES

What session_list does on Yaver

AI agents call session_list 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 session_list is rated Low

This tool retrieves and displays metadata about existing AI agent sessions without creating, modifying, deleting, or executing any operations. It is a straightforward informational query with no side effects, placing it firmly in the Read category. Severity is low because listing sessions poses minimal risk even if misused by an agent—it only exposes metadata about tasks already known to or manageable by the system.

From the tool's definition Tool description explicitly states it 'List[s]' sessions with information like task ID, agent type, title, status, and resumability—a pure retrieval operation with no modification or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs session_list 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 session_list, this is the rule to start with:

session_list Allowed

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

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 session_list call is checked against it from then on.

FAQ

Questions about session_list

What does the session_list tool do? +

List AI agent sessions that can be transferred to another machine. Shows task ID, agent type, title, status, and whether the session is resumable. 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 session_list? +

Register the Yaver 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 Yaver. Nothing to install.

What risk level is session_list? +

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

Can I rate-limit session_list? +

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.

How do I block session_list completely? +

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.

What MCP server provides session_list? +

session_list 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

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 →