This record as markdown: /tools/0xyg3n-claude-c2/privesc-check.md
What privesc_check does on Claude C2
AI agents invoke privesc_check to trigger actions in Claude C2. 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 privesc_check is rated High
Privilege escalation checks actively execute enumeration scripts/commands on remote systems to discover exploitable misconfigurations. Given the broader server context (amsi_bypass, bypassuac, browser_creds, defender_exclude), this is clearly an offensive security/red-team tool.
From the tool's definition 'Check privesc vectors' — privesc (privilege escalation) checks actively probe system configurations, permissions, and vulnerabilities to identify escalation paths; 'Auto-selects client' indicates automated remote execution
Attacks that exploit this kind of access
The rule that runs privesc_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude C2, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For privesc_check, this is the rule to start with:
privesc_check 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude C2, apply this rule, and every privesc_check call is checked against it from then on.
Questions about privesc_check
Check privesc vectors. Auto-selects client. It is categorised as a Execute tool in the Claude C2 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude C2 MCP server in PolicyLayer and add a rule for privesc_check: 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 Claude C2. Nothing to install.
privesc_check 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 privesc_check 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 privesc_check. 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.
privesc_check is provided by the Claude C2 MCP server (0xyg3n/claude-c2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude C2, and thousands of servers like it.
Across the catalogue