background_set_local

Set one strictly validated absolute local image as the background and confirm the Omarchy state symlink. Never downloads or copies files.

SERVEROmarchy-MCP SOURCEhlsitechio/Omarchy-MCP

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/omarchy-mcp/background-set-local.md

WHAT IT DOES

What background_set_local does on Omarchy-MCP

AI agents use background_set_local to create or update resources in Omarchy-MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Omarchy-MCP environment.

RISK

Why background_set_local is rated Medium

Modifies desktop background configuration reversibly without destructive or dangerous side effects.

From the tool's definition Set background, validate absolute local image path, confirm state symlink.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs background_set_local 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 background_set_local, this is the rule to start with:

background_set_local Rate-limited

background_set_local stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "background_set_local": {
      "limits": [
        {
          "counter": "background_set_local_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Omarchy-MCP, apply this rule, and every background_set_local call is checked against it from then on.

FAQ

Questions about background_set_local

What does the background_set_local tool do? +

Set one strictly validated absolute local image as the background and confirm the Omarchy state symlink. Never downloads or copies files. It is categorised as a Write tool in the Omarchy-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on background_set_local? +

Register the Omarchy MCP server in PolicyLayer and add a rule for background_set_local: 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.

What risk level is background_set_local? +

background_set_local is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit background_set_local? +

Yes. Add a rate_limit block to the background_set_local 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.

How do I block background_set_local completely? +

Set action: deny in the PolicyLayer policy for background_set_local. 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.

What MCP server provides background_set_local? +

background_set_local 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.

KEEP EXPLORING

More on Omarchy, and thousands of servers like it.

This server

All 466 Omarchy tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →