Low Risk

get_platform_status

Get platform information including Docker and GPU availability

How to control get_platform_status ↓

What get_platform_status does on vLLM MCP Server

AI agents call get_platform_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.

Low Risk

Why get_platform_status needs a policy

This tool queries system state and returns informational data only. It has no side effects, does not execute commands, modify resources, or trigger external operations. The 'Get' verb and read-only nature confirm this is a Read category tool with low severity.

From the tool's definition Tool description states 'Get platform information' which is a retrieval operation. The function returns status data about Docker, GPU, and platform availability without modifying, executing, or destructing any resources.

Documented attack patterns abuse exactly the kind of access get_platform_status gives an agent:

How to control get_platform_status

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 get_platform_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_platform_status": {}
  }
}

get_platform_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register vLLM MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_platform_status

What does the get_platform_status tool do? +

Get platform information including Docker and GPU availability. It is categorised as a Read tool in the vLLM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_platform_status? +

Register the vLLM MCP Server MCP server in PolicyLayer and add a rule for get_platform_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.

What risk level is get_platform_status? +

get_platform_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_platform_status? +

Yes. Add a rate_limit block to the get_platform_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.

How do I block get_platform_status completely? +

Set action: deny in the PolicyLayer policy for get_platform_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.

What MCP server provides get_platform_status? +

get_platform_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.

Enforce policy on every vLLM MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.