AI agents call vllm_status 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 performs a simple health check and status retrieval of the vLLM server. It queries the current state of the system and returns information with no side effects. This is a classic Read operation: it retrieves data without creating, modifying, executing code, deleting, or moving money.
From the tool's definition Tool name 'vllm_status' and description 'Check the health and status of the vLLM server' indicate a status query operation that retrieves information without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access vllm_status 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 vllm_status:
{
"version": "1",
"default": "deny",
"tools": {
"vllm_status": {}
}
}vllm_status 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.
Check the health and status of the vLLM server. 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 vllm_status: 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.
vllm_status 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 vllm_status 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 vllm_status. 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.
vllm_status 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.