omarchy_network_status
Print active network status for the shell [group:network] Args: [--verbose]
This record as markdown: /tools/omarchy-mcp/omarchy-network-status.md
What omarchy_network_status does on Omarchy-MCP
AI agents call omarchy_network_status 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_network_status is rated Low
Tool queries network status without modification or execution capabilities; read-only operation with informational output.
From the tool's definition Print active network status for the shell, verbose option only
Attacks that exploit this kind of access
The rule that runs omarchy_network_status 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_network_status, this is the rule to start with:
omarchy_network_status 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_network_status call is checked against it from then on.
Questions about omarchy_network_status
Print active network status for the shell [group:network] Args: [--verbose]. 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_network_status: 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_network_status 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_network_status 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_network_status. 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_network_status 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