tmux_close_sessions

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 20 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/tmux-close-sessions.md

WHAT IT DOES

What tmux_close_sessions does on Yaver

AI agents use tmux_close_sessions to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

Parameter	Type	Required	Description
`device_id`	string	—	Optional remote device ID/alias. Empty means this machine.
`all_machines`	boolean	—	Close tmux sessions on all online owned machines.

Parameters from the server's own tool schema.

RISK

Why tmux_close_sessions is rated Medium

An AI agent can call tmux_close_sessions faster than any human can review: one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

tmux_close_sessions Rate-limited

tmux_close_sessions stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tmux_close_sessions": {
      "limits": [
        {
          "counter": "tmux_close_sessions_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about tmux_close_sessions

What does the tmux_close_sessions tool do? +

Kill tmux sessions, closing live Claude/Codex/OpenCode/shell sessions. By default acts on this machine. Pass device_id for one owned remote machine, or all_machines=true to fan out to all online owned machines. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does tmux_close_sessions accept? +

tmux_close_sessions accepts 2 parameters: device_id, all_machines. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tmux_close_sessions? +

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

tmux_close_sessions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit tmux_close_sessions? +

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

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

tmux_close_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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →