split_pane · Post-Exploitation tmux MCP Server MCP

WHAT IT DOES

What split_pane does on Post-Exploitation tmux MCP Server

AI agents invoke split_pane to trigger actions in Post-Exploitation 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 split_pane needs a policy

Splitting a pane in tmux creates a new terminal pane, which is an active modification to the session environment. While not destructive on its own, it establishes a new execution context within a post-exploitation framework, making it an Execute-category action. The server is explicitly described as a 'Post-Exploitation tmux MCP Server', elevating the risk of any execution-enabling action.

From the tool's definition 'Split the current pane in a window' — triggers a tmux pane-split operation, modifying the terminal session layout and potentially enabling new command execution contexts

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

split_pane Rate-limited

split_pane 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": {
    "split_pane": {
      "limits": [
        {
          "counter": "split_pane_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 Post-Exploitation tmux MCP Server, so you can run agents against it safely.

FAQ

Questions about split_pane

What does the split_pane tool do? +

Split the current pane in a window. It is categorised as a Execute tool in the Post-Exploitation 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 split_pane? +

Register the Post-Exploitation tmux MCP Server MCP server in PolicyLayer and add a rule for split_pane: 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 Post-Exploitation tmux MCP Server. Nothing to install.

What risk level is split_pane? +

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

Can I rate-limit split_pane? +

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

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

split_pane is provided by the Post-Exploitation tmux MCP Server MCP server (raghavansv/tmux-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.