omarchy_hyprland_window_width
Save or restore the focused Hyprland window width [group:hyprland] Args: <save|restore>
This record as markdown: /tools/omarchy-mcp/omarchy-hyprland-window-width.md
What omarchy_hyprland_window_width does on Omarchy-MCP
AI agents invoke omarchy_hyprland_window_width 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 omarchy_hyprland_window_width is rated High
Triggers external window manager operations to resize or restore focused window state.
From the tool's definition Save or restore the focused Hyprland window width
Attacks that exploit this kind of access
The rule that runs omarchy_hyprland_window_width 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 omarchy_hyprland_window_width, this is the rule to start with:
omarchy_hyprland_window_width 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 omarchy_hyprland_window_width call is checked against it from then on.
Questions about omarchy_hyprland_window_width
Save or restore the focused Hyprland window width [group:hyprland] Args: <save|restore>. 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 omarchy_hyprland_window_width: 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.
omarchy_hyprland_window_width 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 omarchy_hyprland_window_width 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 omarchy_hyprland_window_width. 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.
omarchy_hyprland_window_width 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