Terminate a specific process identified by its Process ID. Use with caution as this will forcefully terminate the specified process.
AI agents invoke stop_app_by_pid to trigger actions in Wuying AgentBay. 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 triggers external system operations (killing processes by PID) whose effects depend on the provided PID argument. While the action itself is not irreversible in the data sense (processes can be restarted), it performs immediate termination of running applications, which is an Execute action rather than Read or Write. It is not Destructive because no data is permanently deleted or overwritten.
From the tool's definition Tool name 'stop_app_by_pid' and description 'Terminate a specific process identified by its Process ID. Use with caution as this will forcefully terminate the specified process.' directly indicates execution of system-level process termination.
Documented attack patterns abuse exactly the kind of access stop_app_by_pid gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Wuying AgentBay, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_app_by_pid:
{
"version": "1",
"default": "deny",
"tools": {
"stop_app_by_pid": {
"limits": [
{
"counter": "stop_app_by_pid_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_app_by_pid 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.
Terminate a specific process identified by its Process ID. Use with caution as this will forcefully terminate the specified process. It is categorised as a Execute tool in the Wuying AgentBay MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Wuying AgentBay MCP server in PolicyLayer and add a rule for stop_app_by_pid: 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 Wuying AgentBay. Nothing to install.
stop_app_by_pid 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_app_by_pid 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_app_by_pid. 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_app_by_pid is provided by the Wuying AgentBay MCP server (michael98671/agentbay). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Wuying AgentBay, 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.
59 Wuying AgentBay tools catalogued and risk-classified — across an index of 43,000+ MCP servers.