layout_order
Debug view: the placement order (and titles) of tiled windows on the active workspace. Position 1 becomes the master slot in master mode; position 1 is top-left in grid mode.
This record as markdown: /tools/omarchy-mcp/layout-order.md
What layout_order does on Omarchy-MCP
AI agents call layout_order to retrieve information from Omarchy-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why layout_order is rated Low
Queries window layout metadata without modifying state or executing operations; pure information retrieval.
From the tool's definition Debug view: the placement order (and titles) of tiled windows; retrieves window positions.
Attacks that exploit this kind of access
The rule that runs layout_order 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 layout_order, this is the rule to start with:
layout_order is read-only, so it stays allowed. 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 layout_order call is checked against it from then on.
Questions about layout_order
Debug view: the placement order (and titles) of tiled windows on the active workspace. Position 1 becomes the master slot in master mode; position 1 is top-left in grid mode. It is categorised as a Read tool in the Omarchy-MCP MCP Server, which means it retrieves data without modifying state.
Register the Omarchy MCP server in PolicyLayer and add a rule for layout_order: 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.
layout_order is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the layout_order 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 layout_order. 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.
layout_order 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.
This server
Across the catalogue