omarchy_agent_crash

Diagnose a crashed process with the default coding agent [group:agent] Args: <pid> [comm] [exe] [signal]

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/omarchy-agent-crash.md

WHAT IT DOES

What omarchy_agent_crash does on Omarchy-MCP

AI agents invoke omarchy_agent_crash 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 omarchy_agent_crash is rated High

Invokes an AI coding agent to analyze crashes, executing external operations with unpredictable scope.

From the tool's definition Diagnose a crashed process with the default coding agent

Attacks that exploit this kind of access

RECOMMENDED RULE

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

omarchy_agent_crash Rate-limited

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

FAQ

Questions about omarchy_agent_crash

What does the omarchy_agent_crash tool do? +

Diagnose a crashed process with the default coding agent [group:agent] Args: <pid> [comm] [exe] [signal]. 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 omarchy_agent_crash? +

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

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

Can I rate-limit omarchy_agent_crash? +

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

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

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