get-command-result · Ryan's Tmux MCP Server MCP

WHAT IT DOES

What get-command-result does on Ryan's Tmux MCP Server

AI agents invoke get-command-result to trigger actions in Ryan's Tmux MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why get-command-result needs a policy

This tool runs arbitrary commands in a tmux pane and captures their output. Executing arbitrary shell commands in a tmux session is an Execute-category action with high severity, as a misused agent could run any system command, escalate privileges, exfiltrate data, or cause damage depending on the arguments passed.

From the tool's definition "Execute command and capture result from pane" — the tool explicitly executes commands

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

get-command-result Rate-limited

get-command-result stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-command-result": {
      "limits": [
        {
          "counter": "get-command-result_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ryan's Tmux MCP Server, so you can run agents against it safely.

FAQ

Questions about get-command-result

What does the get-command-result tool do? +

Execute command and capture result from pane. It is categorised as a Execute tool in the Ryan's Tmux MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on get-command-result? +

Register the Ryan's Tmux MCP Server MCP server in PolicyLayer and add a rule for get-command-result: 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 Ryan's Tmux MCP Server. Nothing to install.

What risk level is get-command-result? +

get-command-result is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit get-command-result? +

Yes. Add a rate_limit block to the get-command-result 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 get-command-result completely? +

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

get-command-result is provided by the Ryan's Tmux MCP Server MCP server (ryancnelson/ryan-tmux-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.