AI agents use omarchy_theme_set to create or update resources in Omarchy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Omarchy environment.
This tool modifies the current theme setting, which is a reversible write operation. Users can easily switch back to a previous theme. There is no data deletion, code execution, or financial impact. The blast radius is minimal—a misused theme change merely affects desktop appearance and can be undone by setting another theme.
From the tool's definition Tool name 'omarchy_theme_set' and description 'Set the current Omarchy theme' indicate a reversible modification operation. The server context confirms this is a desktop theme management tool without destructive or financial implications.
Attacks that exploit this kind of access
Set the current Omarchy theme. It is categorised as a Write tool in the Omarchy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Omarchy MCP server in PolicyLayer and add a rule for omarchy_theme_set: 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. Nothing to install.
omarchy_theme_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the omarchy_theme_set 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_theme_set. 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_theme_set is provided by the Omarchy MCP server (servicestack/omarchy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →