osd_show

Display a local Omarchy on-screen message or 0-100 progress value and verify that the OSD opened.

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/osd-show.md

WHAT IT DOES

What osd_show does on Omarchy-MCP

AI agents invoke osd_show 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.

RISK

Why osd_show is rated High

Triggers an external UI operation on the desktop, displaying an OSD overlay.

From the tool's definition Display a local Omarchy on-screen message or 0-100 progress value

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs osd_show 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 osd_show, this is the rule to start with:

osd_show Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "osd_show": {
      "limits": [
        {
          "counter": "osd_show_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Omarchy-MCP, apply this rule, and every osd_show call is checked against it from then on.

FAQ

Questions about osd_show

What does the osd_show tool do? +

Display a local Omarchy on-screen message or 0-100 progress value and verify that the OSD opened. 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 osd_show? +

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

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

Can I rate-limit osd_show? +

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

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

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

KEEP EXPLORING

More on Omarchy, and thousands of servers like it.

This server

All 466 Omarchy tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →