request_elevation

What request_elevation does on Procmon

AI agents invoke request_elevation to trigger actions in Procmon. 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.

Why request_elevation is rated High

This tool executes arbitrary code with administrator privileges, making it Execute-category (runs code/commands with external effects). Severity is critical because: (1) UAC elevation grants system-level access enabling modification/deletion of protected files, registry, services, and drivers; (2) misuse could compromise entire system; (3) the blast radius spans installation of malware, privilege escalation attacks,…

From the tool's definition Tool launches commands via UAC elevation (Start-Process -Verb RunAs), executing arbitrary cmd scripts with elevated system privileges. Description explicitly states it runs 'the given command' which can be any shell instruction.

The rule that runs request_elevation safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Procmon, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For request_elevation, this is the rule to start with:

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

Questions about request_elevation