New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

omarchy_setup_factory_reset

Factory-reset this machine back to its freshly-installed state [group:setup] [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-setup-factory-reset.md

What omarchy_setup_factory_reset does on Omarchy-MCP

AI agents call omarchy_setup_factory_reset 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.

Why omarchy_setup_factory_reset is rated Critical

Irreversibly wipes the entire machine back to factory state, catastrophic data loss.

From the tool's definition Factory-reset this machine back to its freshly-installed state

Questions about omarchy_setup_factory_reset

What does the omarchy_setup_factory_reset tool do? +

Factory-reset this machine back to its freshly-installed state [group:setup] [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_setup_factory_reset? +

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

omarchy_setup_factory_reset 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_setup_factory_reset? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Omarchy's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.