omarchy_upgrade_to_quattro

Upgrade a legacy Omarchy install to the package-backed Omarchy quattro layout. [group:upgrade] Args: [--yes] [--reboot] [--dev] [--channel stable|rc|edge] [--user USER] [sudo]

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/omarchy-upgrade-to-quattro.md

WHAT IT DOES

What omarchy_upgrade_to_quattro does on Omarchy-MCP

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

System-wide upgrade with sudo and optional reboot causes irreversible system state changes.

From the tool's definition Upgrade legacy Omarchy install, reboot, channel, sudo

Attacks that exploit this kind of access

RECOMMENDED RULE

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

omarchy_upgrade_to_quattro Rate-limited

omarchy_upgrade_to_quattro 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": {
    "omarchy_upgrade_to_quattro": {
      "limits": [
        {
          "counter": "omarchy_upgrade_to_quattro_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 omarchy_upgrade_to_quattro call is checked against it from then on.

FAQ

Questions about omarchy_upgrade_to_quattro

What does the omarchy_upgrade_to_quattro tool do? +

Upgrade a legacy Omarchy install to the package-backed Omarchy quattro layout. [group:upgrade] Args: [--yes] [--reboot] [--dev] [--channel stable|rc|edge] [--user USER] [sudo]. 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 omarchy_upgrade_to_quattro? +

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

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

Can I rate-limit omarchy_upgrade_to_quattro? +

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

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

omarchy_upgrade_to_quattro 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 →