AI agents invoke stop_psexec_shell 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.
This tool terminates an established remote shell session (PSExec), which is an Execute category action because it triggers external process termination whose effects depend on which session is targeted. While termination itself may seem like cleanup, it directly manipulates running system processes acquired through remote code execution.
From the tool's definition Tool name 'stop_psexec_shell' and description 'Terminates a background PSExec shell session' indicate management of active remote code execution sessions.
Documented attack patterns abuse exactly the kind of access stop_psexec_shell 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 stop_psexec_shell:
{
"version": "1",
"default": "deny",
"tools": {
"stop_psexec_shell": {
"limits": [
{
"counter": "stop_psexec_shell_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_psexec_shell 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.
Terminates a background PSExec shell session. 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 stop_psexec_shell: 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.
stop_psexec_shell 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 stop_psexec_shell 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 stop_psexec_shell. 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.
stop_psexec_shell 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.