Low Risk

list_tmux_sessions

List available tmux sessions

How to control list_tmux_sessions ↓

What list_tmux_sessions does on macOS Notify MCP

AI agents call list_tmux_sessions to retrieve information from macOS Notify MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_tmux_sessions needs a policy

This tool retrieves and enumerates existing tmux sessions. It performs a read-only query with no capability to modify, execute code, delete, or create resources. The blast radius of misuse is minimal — an attacker gains only visibility into active tmux sessions on the system.

From the tool's definition Tool name is 'list_tmux_sessions' and description states 'List available tmux sessions' — a query operation that retrieves information without modification or side effects.

Documented attack patterns abuse exactly the kind of access list_tmux_sessions gives an agent:

How to control list_tmux_sessions

PolicyLayer is an MCP gateway — it sits between your AI agents and macOS Notify MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_tmux_sessions:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_tmux_sessions": {}
  }
}

list_tmux_sessions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register macOS Notify MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_tmux_sessions

What does the list_tmux_sessions tool do? +

List available tmux sessions. It is categorised as a Read tool in the macOS Notify MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_tmux_sessions? +

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

What risk level is list_tmux_sessions? +

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

Can I rate-limit list_tmux_sessions? +

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

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

list_tmux_sessions is provided by the macOS Notify MCP server (yuki-yano/macos-notify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every macOS Notify MCP tool call.

Start from macOS Notify MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

3 macOS Notify MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.