New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

self_window_snap

Float + pin + resize + position OUR OWN host window (found via PID lock) to a corner of a monitor, then verify the result. corner: tl=tr/bl=br or center. No focus stealing; targets by address.

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/self-window-snap.md

What self_window_snap does on Omarchy-MCP

AI agents invoke self_window_snap 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 self_window_snap is rated High

Executes window manager operations to reposition and resize the host application window.

From the tool's definition Float + pin + resize + position OUR OWN host window

Questions about self_window_snap

What does the self_window_snap tool do? +

Float + pin + resize + position OUR OWN host window (found via PID lock) to a corner of a monitor, then verify the result. corner: tl=tr/bl=br or center. No focus stealing; targets by address. 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 self_window_snap? +

Register the Omarchy MCP server in PolicyLayer and add a rule for self_window_snap: 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 self_window_snap? +

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

Can I rate-limit self_window_snap? +

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

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

self_window_snap 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Omarchy's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.