omarchy_update_pkg_prune

Prune superseded versions from the pacman package cache [group:update] [sudo]

SERVEROmarchy-MCP SOURCEhlsitechio/Omarchy-MCP

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/omarchy-mcp/omarchy-update-pkg-prune.md

WHAT IT DOES

What omarchy_update_pkg_prune does on Omarchy-MCP

AI agents call omarchy_update_pkg_prune to permanently remove resources in Omarchy-MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why omarchy_update_pkg_prune is rated Critical

Irreversibly deletes old package cache files; cannot be undone without re-downloading.

From the tool's definition Prune superseded versions from the pacman package cache

Attacks that exploit this kind of access

RECOMMENDED RULE

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

omarchy_update_pkg_prune Hidden

omarchy_update_pkg_prune is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "omarchy_update_pkg_prune"
  ]
}

RESTRICT 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_update_pkg_prune call is checked against it from then on.

FAQ

Questions about omarchy_update_pkg_prune

What does the omarchy_update_pkg_prune tool do? +

Prune superseded versions from the pacman package cache [group:update] [sudo]. It is categorised as a Destructive tool in the Omarchy-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on omarchy_update_pkg_prune? +

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

omarchy_update_pkg_prune is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit omarchy_update_pkg_prune? +

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

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

omarchy_update_pkg_prune 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 → Critical-risk tools on this server →

Across the catalogue

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

Guides

Govern database agents →Blast radius →Tool call approval →