AI agents invoke stop-process to trigger actions in Https://github Com/Streen9/react. 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.
Stopping a process is an Execute action because it triggers an external system operation (process termination) whose effects depend on which process is targeted. While termination is not data deletion (which would be Destructive), it irreversibly halts execution and can disrupt services, workflows, or applications.
From the tool's definition Tool is named 'stop-process' with description 'Stop a running process'. This performs an irreversible action that terminates a running process, affecting external operations and their state.
Documented attack patterns abuse exactly the kind of access stop-process gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Https://github Com/Streen9/react, and nothing reaches the server without passing your rules. This is the rule we recommend for stop-process:
{
"version": "1",
"default": "deny",
"tools": {
"stop-process": {
"limits": [
{
"counter": "stop-process_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop-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.
Stop a running process. It is categorised as a Execute tool in the Https://github Com/Streen9/react MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Https://github Com/Streen9/react MCP server in PolicyLayer and add a rule for stop-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 Https://github Com/Streen9/react. Nothing to install.
stop-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-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-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-process is provided by the Https://github Com/Streen9/react MCP server (kalivaraprasad-gonapa/react-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Https://github Com/Streen9/react, 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.
9 Https://github Com/Streen9/react tools catalogued and risk-classified — across an index of 43,000+ MCP servers.