tmux_stream

Return a bounded snapshot of live tmux pane state (working / awaiting-input / idle / dead / no-agent). Pass session, pane (like %37), or leave empty for all panes. MCP calls are request/response; native/web clients needing continuous updates use the authenticated GET /tmux/stream SSE route.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 20 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-stream.md

WHAT IT DOES

What tmux_stream does on Yaver

AI agents call tmux_stream 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.

Parameter	Type	Required	Description
`pane`	string	—	Optional tmux pane id (e.g. %37) to watch.
`session`	string	—	Optional tmux session name to watch (its active pane).

Parameters from the server's own tool schema.

RISK

Why tmux_stream is rated Low

Retrieves read-only status of tmux panes without modification or side effects.

From the tool's definition Return a bounded snapshot of live tmux pane state

Attacks that exploit this kind of access

RECOMMENDED RULE

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

tmux_stream Allowed

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

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

FAQ

Questions about tmux_stream

What does the tmux_stream tool do? +

What parameters does tmux_stream accept? +

tmux_stream accepts 2 parameters: pane, session. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tmux_stream? +

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

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

Can I rate-limit tmux_stream? +

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

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

tmux_stream 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

The MCP Attack Database →

Guides

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