This record as markdown: /tools/rsp2k-mcp-vultr/list-voc-plans.md
What list_voc_plans does on Vultr MCP
AI agents call list_voc_plans 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_voc_plans is rated Low
This tool retrieves or queries information about VOC plans—a passive read operation with no side effects, state changes, or irreversible actions. It matches the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because misuse would only expose pricing or plan metadata, not sensitive credentials or customer data, and carries no blast radius for…
From the tool's definition Tool name 'list_voc_plans' and description 'List VOC (Optimized Cloud) plans' indicate a retrieval operation that queries available plans without modifying any data.
Attacks that exploit this kind of access
The rule that runs list_voc_plans 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_voc_plans, this is the rule to start with:
list_voc_plans 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_voc_plans call is checked against it from then on.
Questions about list_voc_plans
List VOC (Optimized Cloud) plans. 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_voc_plans: 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_voc_plans 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_voc_plans 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_voc_plans. 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_voc_plans 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