This record as markdown: /tools/rsp2k-mcp-vultr/list-windows-os.md
What list_windows_os does on Vultr MCP
AI agents call list_windows_os to retrieve information from Vultr MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_windows_os is rated Low
This tool retrieves or queries available Windows operating systems without modifying, deleting, or executing any operations. It is informational only, making it a straightforward Read category tool with low severity risk. The confidence is high because the intent is unambiguous.
From the tool's definition Tool name 'list_windows_os' and description 'List Windows operating systems' indicate a query/retrieval operation with no side effects. The verb 'list' is a clear indicator of Read category operations.
Attacks that exploit this kind of access
The rule that runs list_windows_os safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_windows_os, this is the rule to start with:
list_windows_os is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every list_windows_os call is checked against it from then on.
Questions about list_windows_os
List Windows operating systems. It is categorised as a Read tool in the Vultr MCP MCP Server, which means it retrieves data without modifying state.
Register the Vultr MCP server in PolicyLayer and add a rule for list_windows_os: 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 Vultr MCP. Nothing to install.
list_windows_os 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_windows_os 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_windows_os. 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_windows_os is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vultr, and thousands of servers like it.
This server
Across the catalogue