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

omarchy_setup_security_sshd

Set up the OpenSSH server, open the firewall, and authorize an SSH key [group:setup] Args: [--key=<public-key>] [sudo]

SERVEROmarchy-MCP SOURCEhlsitechio/Omarchy-MCP
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/omarchy-mcp/omarchy-setup-security-sshd.md

What omarchy_setup_security_sshd does on Omarchy-MCP

AI agents invoke omarchy_setup_security_sshd to trigger actions in Omarchy-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why omarchy_setup_security_sshd is rated High

Installs SSH server, modifies firewall rules, and authorizes remote access keys — severe system exposure.

From the tool's definition Set up OpenSSH server, open firewall, authorize SSH key

Questions about omarchy_setup_security_sshd

What does the omarchy_setup_security_sshd tool do? +

Set up the OpenSSH server, open the firewall, and authorize an SSH key [group:setup] Args: [--key=<public-key>] [sudo]. It is categorised as a Execute tool in the Omarchy-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on omarchy_setup_security_sshd? +

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

omarchy_setup_security_sshd is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit omarchy_setup_security_sshd? +

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

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

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