Launch a cmd script via UAC (Start-Process -Verb RunAs) to run the given command.
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.
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.
Documented attack patterns abuse exactly the kind of access request_elevation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Procmon, and nothing reaches the server without passing your rules. This is the rule we recommend for request_elevation:
{
"version": "1",
"default": "deny",
"tools": {
"request_elevation": {
"limits": [
{
"counter": "request_elevation_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}request_elevation 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.
Free to start. No card required.
Launch a cmd script via UAC (Start-Process -Verb RunAs) to run the given command. It is categorised as a Execute tool in the Procmon MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Procmon MCP server in PolicyLayer and add a rule for request_elevation: 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 Procmon. Nothing to install.
request_elevation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the request_elevation 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.
Set action: deny in the PolicyLayer policy for request_elevation. 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.
request_elevation is provided by the Procmon MCP server (0xhackerfren/procmon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Procmon tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Procmon tools catalogued and risk-classified — across an index of 42,500+ MCP servers.