get_availability

A read tool on the Vultr MCP server.

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/get-availability.md

WHAT IT DOES

What get_availability does on Vultr MCP

AI agents call get_availability 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 get_availability is rated Low

Based on the tool name following the 'get_*' pattern, this is most likely a data retrieval operation that queries availability information (such as available regions, services, or capacity). It has no documented write, delete, or execute capabilities. The low severity reflects that reading availability data poses minimal risk even if misused by an agent, as it cannot modify or delete resources.

From the tool's definition Tool name 'get_availability' suggests a retrieval operation. The verb 'get' indicates a query action without side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_availability Allowed

get_availability 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": {
    "get_availability": {}
  }
}

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 get_availability call is checked against it from then on.

FAQ

Questions about get_availability

What does the get_availability tool do? +

get_availability is a read tool on the Vultr MCP server. 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 get_availability? +

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

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

Can I rate-limit get_availability? +

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

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

get_availability 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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