New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_plan_by_type_and_spec

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

Questions about get_plan_by_type_and_spec

What does the get_plan_by_type_and_spec tool do? +

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.

How do I enforce a policy on get_plan_by_type_and_spec? +

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.

What risk level is get_plan_by_type_and_spec? +

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

Can I rate-limit get_plan_by_type_and_spec? +

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.

How do I block get_plan_by_type_and_spec completely? +

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.

What MCP server provides get_plan_by_type_and_spec? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Vultr's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.