Clarify that MCP Safety controls tool visibility, not OS-level confinement.

Open
#127 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
58/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation, security

Research direction

Start by locating the documentation or UX text that describes MCP Safety and tmux tool visibility. Clarify that the controls scope tmux and MCP operations rather than OS-level confinement, and state that tmux and agents can still invoke shell commands; done when the wording no longer implies security isolation.

Written by the indexing model from the issue text.

Description

For evening / weekends:

The title says it, but tmux can execute commands through formatters and send-keys, so that security assurances are really tool-level scoping for tmux operations, not OS-level commands. The scoping are tmux and MCP specific - tmux is still a raw command tool.

We should have a way to convey this clearly in the UX of the docs.

MCP / tmux: tmux operations

Note: Tmux, and AI agents themselves can still invoke and run shell commands.

it may be worth not phrasing it as safety / security at all and calling them tool types - as the surface / llm can already make commands.

Dominant language
Python
Stars
13
Forks
0
Avg merge
13h 52m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tmux-python/libtmux-mcp

All issues in tmux-python/libtmux-mcp

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.