omarchy_commands
Search the machine-readable command catalog from the installed Omarchy version. Useful for discovering the correct current route and arguments before adding or troubleshooting a wrapper.
This record as markdown: /tools/omarchy-mcp/omarchy-commands.md
What omarchy_commands does on Omarchy-MCP
AI agents call omarchy_commands to retrieve information from Omarchy-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why omarchy_commands is rated Low
Tool queries static command metadata without executing commands or modifying system state.
From the tool's definition Search the machine-readable command catalog from the installed Omarchy version.
Attacks that exploit this kind of access
The rule that runs omarchy_commands 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_commands, this is the rule to start with:
omarchy_commands is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Omarchy-MCP, apply this rule, and every omarchy_commands call is checked against it from then on.
Questions about omarchy_commands
Search the machine-readable command catalog from the installed Omarchy version. Useful for discovering the correct current route and arguments before adding or troubleshooting a wrapper. It is categorised as a Read tool in the Omarchy-MCP MCP Server, which means it retrieves data without modifying state.
Register the Omarchy MCP server in PolicyLayer and add a rule for omarchy_commands: 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_commands is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the omarchy_commands 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_commands. 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_commands 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.
This server
Across the catalogue