Low Risk

list_os_by_family

List operating systems by family.

How to control list_os_by_family ↓

What list_os_by_family does on Vultr MCP

AI agents call list_os_by_family to retrieve information from Vultr MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_os_by_family needs a policy

This tool retrieves or lists available operating system families without creating, modifying, executing, or deleting any infrastructure. It is a read-only data retrieval operation with minimal blast radius if misused—an AI agent cannot cause harm by listing OS families.

From the tool's definition Tool name 'list_os_by_family' and description 'List operating systems by family' indicate a query/retrieval operation with no modification or execution of resources.

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

How to control list_os_by_family

PolicyLayer is an MCP gateway — it sits between your AI agents and Vultr MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for list_os_by_family:

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

list_os_by_family 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 Vultr MCP — 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 list_os_by_family

What does the list_os_by_family tool do? +

List operating systems by family. It is categorised as a Read tool in the Vultr MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_os_by_family? +

Register the Vultr MCP server in PolicyLayer and add a rule for list_os_by_family: 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.

What risk level is list_os_by_family? +

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

Can I rate-limit list_os_by_family? +

Yes. Add a rate_limit block to the list_os_by_family 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 list_os_by_family completely? +

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

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

Enforce policy on every Vultr MCP tool call.

Start from Vultr MCP, 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.

284 Vultr MCP 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.