tmux_list_sessions

List all tmux sessions on this machine with agent detection (claude, codex, aider, etc.) and their relationship to Yaver (adopted, forked-by-yaver, unrelated).

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

WHAT IT DOES

What tmux_list_sessions does on Yaver

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

Tool retrieves session metadata without modifying or executing operations; read-only introspection.

From the tool's definition List all tmux sessions on this machine with agent detection

Attacks that exploit this kind of access

RECOMMENDED RULE

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

tmux_list_sessions Allowed

tmux_list_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": {
    "tmux_list_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 tmux_list_sessions call is checked against it from then on.

FAQ

Questions about tmux_list_sessions

What does the tmux_list_sessions tool do? +

List all tmux sessions on this machine with agent detection (claude, codex, aider, etc.) and their relationship to Yaver (adopted, forked-by-yaver, unrelated). 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 tmux_list_sessions? +

Register the Yaver MCP server in PolicyLayer and add a rule for tmux_list_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 tmux_list_sessions? +

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

Can I rate-limit tmux_list_sessions? +

Yes. Add a rate_limit block to the tmux_list_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 tmux_list_sessions completely? +

Set action: deny in the PolicyLayer policy for tmux_list_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 tmux_list_sessions? +

tmux_list_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 678 Yaver tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

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