plugin_local_detail

Inspect one already-discovered local plugin, its sanitized manifest, runtime state, and bar location. No URLs or network access are used.

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-detail.md

WHAT IT DOES

What plugin_local_detail does on Omarchy-MCP

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

An AI agent can call plugin_local_detail faster than any human can review: one bad instruction and it creates or modifies resources in Omarchy-MCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

plugin_local_detail Rate-limited

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

FAQ

Questions about plugin_local_detail

What does the plugin_local_detail tool do? +

Inspect one already-discovered local plugin, its sanitized manifest, runtime state, and bar location. No URLs or network access are used. 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_detail? +

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

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

Can I rate-limit plugin_local_detail? +

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

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

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