workspace_layout
Switch a workspace between the MCP grid, Hyprland dwindle, master, or scrolling tiling engine and verify tiledLayout. Use dwindle before layout_preselect/open_window_split; use omarchy-grid for deterministic grids.
This record as markdown: /tools/omarchy-mcp/workspace-layout.md
What workspace_layout does on Omarchy-MCP
AI agents invoke workspace_layout 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.
Why workspace_layout is rated High
Changes active workspace layout configuration, triggering external desktop environment operations.
From the tool's definition Switch a workspace between... tiling engine and verify tiledLayout
Attacks that exploit this kind of access
The rule that runs workspace_layout 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 workspace_layout, this is the rule to start with:
workspace_layout 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Omarchy-MCP, apply this rule, and every workspace_layout call is checked against it from then on.
Questions about workspace_layout
Switch a workspace between the MCP grid, Hyprland dwindle, master, or scrolling tiling engine and verify tiledLayout. Use dwindle before layout_preselect/open_window_split; use omarchy-grid for deterministic grids. 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.
Register the Omarchy MCP server in PolicyLayer and add a rule for workspace_layout: 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.
workspace_layout is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the workspace_layout 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.
Set action: deny in the PolicyLayer policy for workspace_layout. 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.
workspace_layout 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.
More on Omarchy, and thousands of servers like it.
Across the catalogue