omarchy_install_gaming_steam
Install Steam and graphics drivers selected for this system [group:install] [sudo]
This record as markdown: /tools/omarchy-mcp/omarchy-install-gaming-steam.md
What omarchy_install_gaming_steam does on Omarchy-MCP
AI agents invoke omarchy_install_gaming_steam 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_install_gaming_steam is rated High
Installs system-level software and drivers with elevated privileges, making significant system changes.
From the tool's definition Install Steam and graphics drivers, sudo
Attacks that exploit this kind of access
The rule that runs omarchy_install_gaming_steam 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_install_gaming_steam, this is the rule to start with:
omarchy_install_gaming_steam stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_install_gaming_steam call is checked against it from then on.
Questions about omarchy_install_gaming_steam
Install Steam and graphics drivers selected for this system [group:install] [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.
Register the Omarchy MCP server in PolicyLayer and add a rule for omarchy_install_gaming_steam: 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_install_gaming_steam is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the omarchy_install_gaming_steam 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_install_gaming_steam. 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_install_gaming_steam 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.
Across the catalogue