AI agents invoke stop_vllm to trigger actions in vLLM MCP Server. 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 a destructive operational command (stop/terminate) against infrastructure. While technically reversible (the container can be restarted), it immediately halts services and operations with significant blast radius - all active inference requests, connections, and workloads are interrupted.
From the tool's definition Stop a running vLLM Docker container - directly controls container lifecycle and terminates running processes
Documented attack patterns abuse exactly the kind of access stop_vllm gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and vLLM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_vllm:
{
"version": "1",
"default": "deny",
"tools": {
"stop_vllm": {
"limits": [
{
"counter": "stop_vllm_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_vllm 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 vLLM Docker container. It is categorised as a Execute tool in the vLLM MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the vLLM MCP Server MCP server in PolicyLayer and add a rule for stop_vllm: 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 vLLM MCP Server. Nothing to install.
stop_vllm 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_vllm 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_vllm. 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_vllm is provided by the vLLM MCP Server MCP server (micytao/vllm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from vLLM MCP Server, 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.
12 vLLM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.