Whether the server is elevated plus a capability matrix for all tools.
AI agents call check_elevation to retrieve information from Procmon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns elevation status and capability information. It performs no side effects, creates no data modifications, executes no code, and performs no destructive operations. It is purely informational—a status check that returns data about the server's current privilege level and what tools can do. This is a classic Read operation (get/fetch pattern).
From the tool's definition Tool name 'check_elevation' and description 'Whether the server is elevated plus a capability matrix for all tools' indicate a read-only query that retrieves status information and displays a capability matrix without modifying, executing, or deleting…
Documented attack patterns abuse exactly the kind of access check_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 check_elevation:
{
"version": "1",
"default": "deny",
"tools": {
"check_elevation": {}
}
}check_elevation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Whether the server is elevated plus a capability matrix for all tools. It is categorised as a Read tool in the Procmon MCP Server, which means it retrieves data without modifying state.
Register the Procmon MCP server in PolicyLayer and add a rule for check_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.
check_elevation is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_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 check_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.
check_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.