AI agents invoke run_psexec to trigger actions in Pentester-MCP. 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.
PsExec executes arbitrary commands on remote systems, making this an Execute category tool. Severity is critical because: (1) remote command execution has unlimited blast radius depending on injected commands, (2) it can pivot across networks, (3) it can escalate privileges, (4) an AI agent with this tool could execute destructive or malicious payloads without explicit user intent.
From the tool's definition Tool name 'run_psexec' refers to PsExec, a legitimate penetration testing utility that executes commands remotely on Windows systems.
Documented attack patterns abuse exactly the kind of access run_psexec gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pentester-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for run_psexec:
{
"version": "1",
"default": "deny",
"tools": {
"run_psexec": {
"limits": [
{
"counter": "run_psexec_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run_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.
Free to start. No card required.
run_psexec. It is categorised as a Execute tool in the Pentester-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pentester- MCP server in PolicyLayer and add a rule for run_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 Pentester-MCP. Nothing to install.
run_psexec 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 run_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.
Set action: deny in the PolicyLayer policy for run_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.
run_psexec is provided by the Pentester- MCP server (halilkirazkaya/pentester-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pentester-MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
337 Pentester-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.