list_available_versions

List available versions for database engine upgrades.

SERVERVultr MCP SOURCErsp2k/mcp-vultr

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rsp2k-mcp-vultr/list-available-versions.md

WHAT IT DOES

What list_available_versions does on Vultr MCP

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

RISK

Why list_available_versions is rated Low

This tool queries and returns information about available database engine versions without modifying, deleting, or executing any infrastructure changes. It is purely informational and read-only, making it a standard Read category tool with low severity since misuse would only expose version information without causing operational impact.

From the tool's definition Tool name 'list_available_versions' and description 'List available versions for database engine upgrades' both indicate a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_available_versions 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_available_versions, this is the rule to start with:

list_available_versions Allowed

list_available_versions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_available_versions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every list_available_versions call is checked against it from then on.

FAQ

Questions about list_available_versions

What does the list_available_versions tool do? +

List available versions for database engine upgrades. 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_available_versions? +

Register the Vultr MCP server in PolicyLayer and add a rule for list_available_versions: 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_available_versions? +

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

Can I rate-limit list_available_versions? +

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

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

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

KEEP EXPLORING

More on Vultr, and thousands of servers like it.

This server

All 284 Vultr tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →