omarchy_capture_screenshot
Take a screenshot [group:capture] Args: [smart|region|windows|fullscreen] [slurp|copy|save] [--editor=<name>]
This record as markdown: /tools/omarchy-mcp/omarchy-capture-screenshot.md
What omarchy_capture_screenshot does on Omarchy-MCP
AI agents call omarchy_capture_screenshot 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 omarchy_capture_screenshot is rated Low
Screenshots retrieve visual data without modifying system state or data.
From the tool's definition Take a screenshot; capture group; read-only desktop state
Attacks that exploit this kind of access
The rule that runs omarchy_capture_screenshot 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_capture_screenshot, this is the rule to start with:
omarchy_capture_screenshot 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 omarchy_capture_screenshot call is checked against it from then on.
Questions about omarchy_capture_screenshot
Take a screenshot [group:capture] Args: [smart|region|windows|fullscreen] [slurp|copy|save] [--editor=<name>]. 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 omarchy_capture_screenshot: 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_capture_screenshot 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 omarchy_capture_screenshot 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_capture_screenshot. 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_capture_screenshot 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