plugin_local_enable

Enable an already-discovered plugin. Bar widgets require an exact section/index; bar replacements are refused. Defaults to dry-run.

SERVEROmarchy-MCP SOURCEhlsitechio/Omarchy-MCP

High RISK CLASS

Category Execute

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/plugin-local-enable.md

WHAT IT DOES

What plugin_local_enable does on Omarchy-MCP

AI agents invoke plugin_local_enable 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.

RISK

Why plugin_local_enable is rated High

Activating a plugin triggers external system changes with potentially broad desktop effects.

From the tool's definition Enable an already-discovered plugin, bar widgets require exact section/index

Attacks that exploit this kind of access

RECOMMENDED RULE

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

plugin_local_enable Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "plugin_local_enable": {
      "limits": [
        {
          "counter": "plugin_local_enable_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 plugin_local_enable call is checked against it from then on.

FAQ

Questions about plugin_local_enable

What does the plugin_local_enable tool do? +

Enable an already-discovered plugin. Bar widgets require an exact section/index; bar replacements are refused. Defaults to dry-run. 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.

How do I enforce a policy on plugin_local_enable? +

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

plugin_local_enable is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit plugin_local_enable? +

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

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

plugin_local_enable 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →