open_window_split

Preselect a split direction and launch a command, then VERIFY on-screen that the new window actually tiled into that split. Returns the landed window

SERVEROmarchy-MCP SOURCEhlsitechio/Omarchy-MCP

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/omarchy-mcp/open-window-split.md

WHAT IT DOES

What open_window_split does on Omarchy-MCP

AI agents invoke open_window_split to trigger actions in Omarchy-MCP. 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.

RISK

Why open_window_split is rated High

Launches arbitrary commands on the desktop, executing external operations with variable effects.

From the tool's definition launch a command, preselect split direction, VERIFY on-screen

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs open_window_split safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Omarchy-MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For open_window_split, this is the rule to start with:

open_window_split Rate-limited

open_window_split 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": {
    "open_window_split": {
      "limits": [
        {
          "counter": "open_window_split_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about open_window_split

What does the open_window_split tool do? +

Preselect a split direction and launch a command, then VERIFY on-screen that the new window actually tiled into that split. Returns the landed window. It is categorised as a Execute tool in the Omarchy-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on open_window_split? +

Register the Omarchy MCP server in PolicyLayer and add a rule for open_window_split: 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 Omarchy-MCP. Nothing to install.

What risk level is open_window_split? +

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

Can I rate-limit open_window_split? +

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

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

open_window_split is provided by the Omarchy MCP server (hlsitechio/Omarchy-MCP). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Omarchy, and thousands of servers like it.

This server

All 466 Omarchy tools → High-risk tools on this server →

Across the catalogue

focus_window on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →