AI agents call list_vllm_containers to retrieve information from vLLM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about existing Docker containers without creating, modifying, deleting, or executing any operations. It is purely informational and presents no side effects beyond reading container metadata.
From the tool's definition Tool name 'list_vllm_containers' and description 'List all vLLM Docker containers' indicate a querying/listing operation with no modification or execution of container operations.
Documented attack patterns abuse exactly the kind of access list_vllm_containers 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 list_vllm_containers:
{
"version": "1",
"default": "deny",
"tools": {
"list_vllm_containers": {}
}
}list_vllm_containers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all vLLM Docker containers. It is categorised as a Read tool in the vLLM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the vLLM MCP Server MCP server in PolicyLayer and add a rule for list_vllm_containers: 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.
list_vllm_containers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_vllm_containers 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 list_vllm_containers. 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.
list_vllm_containers 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.