omarchy_remove_dev_env

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-remove-dev-env.md

WHAT IT DOES

What omarchy_remove_dev_env does on Omarchy-MCP

AI agents call omarchy_remove_dev_env 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_remove_dev_env is rated Critical

Irreversibly deletes installed development environments and associated configurations without undo capability.

From the tool's definition Remove a development environment that was previously installed

Attacks that exploit this kind of access

RECOMMENDED RULE

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

omarchy_remove_dev_env Hidden

omarchy_remove_dev_env 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_remove_dev_env"
  ]
}

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

FAQ

Questions about omarchy_remove_dev_env

What does the omarchy_remove_dev_env tool do? +

How do I enforce a policy on omarchy_remove_dev_env? +

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

omarchy_remove_dev_env 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_remove_dev_env? +

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

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

omarchy_remove_dev_env 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

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →