theme_bg_next
Switch to the next background, verify it, and automatically restore the prior theme and content-identical wallpaper after any mutation failure.
This record as markdown: /tools/omarchy-mcp/theme-bg-next.md
What theme_bg_next does on Omarchy-MCP
AI agents invoke theme_bg_next 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 theme_bg_next is rated High
Triggers desktop background switching with verification and rollback logic.
From the tool's definition Switch to next background, verify it, automatically restore prior theme
Attacks that exploit this kind of access
The rule that runs theme_bg_next 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 theme_bg_next, this is the rule to start with:
theme_bg_next 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 theme_bg_next call is checked against it from then on.
Questions about theme_bg_next
Switch to the next background, verify it, and automatically restore the prior theme and content-identical wallpaper after any mutation failure. 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 theme_bg_next: 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.
theme_bg_next 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 theme_bg_next 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 theme_bg_next. 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.
theme_bg_next 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