omarchy_tui_remove
Remove a terminal UI desktop launcher [group:tui] Args: [name]
This record as markdown: /tools/omarchy-mcp/omarchy-tui-remove.md
What omarchy_tui_remove does on Omarchy-MCP
AI agents call omarchy_tui_remove 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_tui_remove is rated Critical
Permanently removes desktop launchers without undo capability; high disruption to desktop functionality and usability.
From the tool's definition Remove a terminal UI desktop launcher; irreversibly deletes launcher from system.
Attacks that exploit this kind of access
The rule that runs omarchy_tui_remove 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_tui_remove, this is the rule to start with:
omarchy_tui_remove 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_tui_remove call is checked against it from then on.
Questions about omarchy_tui_remove
Remove a terminal UI desktop launcher [group:tui] Args: [name]. 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_tui_remove: 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_tui_remove 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_tui_remove 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_tui_remove. 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_tui_remove 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