psexec · Claude C2 MCP: Risk & Policy

WHAT IT DOES

What psexec does on Claude C2

AI agents invoke psexec 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 IT NEEDS A POLICY

Why psexec needs a policy

PsExec enables arbitrary remote code execution on target systems. In the context of this server (which also exposes tools like amsi_bypass, bypassuac, browser_creds, and defender_exclude), this is clearly a command-and-control capability. Misuse could allow full system compromise of remote machines.

From the tool's definition 'PsExec remote execution' — PsExec is a well-known Sysinternals tool used to execute processes on remote systems, often leveraged in lateral movement and remote command execution scenarios.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

psexec Rate-limited

psexec 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": {
    "psexec": {
      "limits": [
        {
          "counter": "psexec_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude C2, so you can run agents against it safely.

FAQ

Questions about psexec

What does the psexec tool do? +

PsExec remote execution. 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.

How do I enforce a policy on psexec? +

Register the Claude C2 MCP server in PolicyLayer and add a rule for psexec: 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.

What risk level is psexec? +

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

Can I rate-limit psexec? +

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

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

psexec 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.

// THE FULL RECORD

psexec is one line of Claude C2's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →