Terminates a background wget process using its PID.
AI agents invoke stop_wget_process 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 executes system-level process termination commands (likely SIGTERM or SIGKILL via kill-like syscalls). Although it appears benign in isolation—stopping a download is reversible—it falls under Execute rather than Write because it triggers external OS operations whose effects depend on which process is targeted by the provided PID.
From the tool's definition Tool name 'stop_wget_process' and description 'Terminates a background wget process using its PID' indicate process control/termination capability.
Documented attack patterns abuse exactly the kind of access stop_wget_process 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_wget_process:
{
"version": "1",
"default": "deny",
"tools": {
"stop_wget_process": {
"limits": [
{
"counter": "stop_wget_process_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_wget_process 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 wget process using its PID. 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_wget_process: 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_wget_process 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_wget_process 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_wget_process. 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_wget_process 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.