plugin_local_disable

Disable a reversible local plugin and verify catalog/bar state. Critical first-party services and active bars are refused. Defaults to dry-run.

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

WHAT IT DOES

What plugin_local_disable does on Omarchy-MCP

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

Reversibly disables plugins with safeguards; Write-level impact with guardrails prevents critical service damage.

From the tool's definition Disable a reversible local plugin, defaults to dry-run

Attacks that exploit this kind of access

RECOMMENDED RULE

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

plugin_local_disable Rate-limited

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

FAQ

Questions about plugin_local_disable

What does the plugin_local_disable tool do? +

Disable a reversible local plugin and verify catalog/bar state. Critical first-party services and active bars are refused. Defaults to dry-run. 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 plugin_local_disable? +

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

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

Can I rate-limit plugin_local_disable? +

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

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

plugin_local_disable 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 →