omarchy_setup_factory_reset
Factory-reset this machine back to its freshly-installed state [group:setup] [sudo]
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
Attacks that exploit this kind of access
The rule that runs omarchy_setup_factory_reset 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_setup_factory_reset, this is the rule to start with:
omarchy_setup_factory_reset is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Omarchy-MCP, apply this rule, and every omarchy_setup_factory_reset call is checked against it from then on.
Questions about omarchy_setup_factory_reset
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.
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.
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.
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.
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.
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.
Across the catalogue