system_resource_stats
Read Omarchy CPU/memory statistics plus local load averages and uptime. Read-only and offline.
This record as markdown: /tools/omarchy-mcp/system-resource-stats.md
What system_resource_stats does on Omarchy-MCP
AI agents call system_resource_stats 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 system_resource_stats is rated Low
Retrieves system statistics without modification or side effects.
From the tool's definition Read-only, offline, CPU/memory statistics, load averages, uptime
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_resource_stats 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 system_resource_stats, this is the rule to start with:
system_resource_stats 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 system_resource_stats call is checked against it from then on.
Questions about system_resource_stats
Read Omarchy CPU/memory statistics plus local load averages and uptime. Read-only and offline. 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 system_resource_stats: 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.
system_resource_stats 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 system_resource_stats 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 system_resource_stats. 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.
system_resource_stats 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