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

omarchy_remove_security_sudoless_docker

Disable sudoless Docker by removing your user from the docker group [group:remove] [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-remove-security-sudoless-docker.md

What omarchy_remove_security_sudoless_docker does on Omarchy-MCP

AI agents call omarchy_remove_security_sudoless_docker 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_remove_security_sudoless_docker is rated Critical

Irreversibly removes user from docker group, revoking sudoless Docker access permanently.

From the tool's definition Disable sudoless Docker by removing your user from the docker group

Questions about omarchy_remove_security_sudoless_docker

What does the omarchy_remove_security_sudoless_docker tool do? +

Disable sudoless Docker by removing your user from the docker group [group:remove] [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_remove_security_sudoless_docker? +

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

omarchy_remove_security_sudoless_docker 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_security_sudoless_docker? +

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

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

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