omarchy_refresh_config

Copy a shipped user config from $OMARCHY_PATH/config into ~/.config (backs up your version). [group:refresh] Args: <config-path>

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/omarchy-refresh-config.md

WHAT IT DOES

What omarchy_refresh_config does on Omarchy-MCP

AI agents use omarchy_refresh_config 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 omarchy_refresh_config is rated Medium

Modifies user configuration files reversibly with automatic backup, affecting system behavior and preferences.

From the tool's definition Copy shipped config into ~/.config, backs up existing version

Attacks that exploit this kind of access

RECOMMENDED RULE

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

omarchy_refresh_config Rate-limited

omarchy_refresh_config 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": {
    "omarchy_refresh_config": {
      "limits": [
        {
          "counter": "omarchy_refresh_config_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 omarchy_refresh_config call is checked against it from then on.

FAQ

Questions about omarchy_refresh_config

What does the omarchy_refresh_config tool do? +

Copy a shipped user config from $OMARCHY_PATH/config into ~/.config (backs up your version). [group:refresh] Args: <config-path>. 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 omarchy_refresh_config? +

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

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

Can I rate-limit omarchy_refresh_config? +

Yes. Add a rate_limit block to the omarchy_refresh_config 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 omarchy_refresh_config completely? +

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

omarchy_refresh_config 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

The MCP Attack Database →

Guides

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