get_plan_by_type_and_spec
A read tool on the Vultr MCP server.
This record as markdown: /tools/rsp2k-mcp-vultr/get-plan-by-type-and-spec.md
What get_plan_by_type_and_spec does on Vultr MCP
AI agents call get_plan_by_type_and_spec 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 get_plan_by_type_and_spec is rated Low
The tool appears designed to fetch or query plan details—a read-only operation with no side effects. The 'get_' prefix and absence of descriptive text prevent certainty, but the naming pattern strongly suggests data retrieval.
From the tool's definition Tool name 'get_plan_by_type_and_spec' indicates retrieval of plan information based on query parameters (type and spec). No mutation, deletion, or execution keywords present.
Attacks that exploit this kind of access
The rule that runs get_plan_by_type_and_spec 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_plan_by_type_and_spec, this is the rule to start with:
get_plan_by_type_and_spec 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 get_plan_by_type_and_spec call is checked against it from then on.
Questions about get_plan_by_type_and_spec
get_plan_by_type_and_spec 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.
Register the Vultr MCP server in PolicyLayer and add a rule for get_plan_by_type_and_spec: 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.
get_plan_by_type_and_spec 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 get_plan_by_type_and_spec 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 get_plan_by_type_and_spec. 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.
get_plan_by_type_and_spec 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