plugin_validate

Validate a local plugin folder against Omarchy

SERVEROmarchy-MCP SOURCEhlsitechio/Omarchy-MCP

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/omarchy-mcp/plugin-validate.md

WHAT IT DOES

What plugin_validate does on Omarchy-MCP

AI agents call plugin_validate to retrieve information from Omarchy-MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why plugin_validate is rated Low

Validation reads and checks plugin folder contents without modifying or executing anything.

From the tool's definition Validate a local plugin folder against Omarchy

Attacks that exploit this kind of access

RECOMMENDED RULE

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

plugin_validate Allowed

plugin_validate is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "plugin_validate": {}
  }
}

ALLOW ONLY 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_validate call is checked against it from then on.

FAQ

Questions about plugin_validate

What does the plugin_validate tool do? +

Validate a local plugin folder against Omarchy. It is categorised as a Read tool in the Omarchy-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on plugin_validate? +

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

plugin_validate is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit plugin_validate? +

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

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

plugin_validate 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

Roll out MCP under one policy →Data exfiltration →MCP token cost →