search_plans_by_specs
AI agents call search_plans_by_specs to retrieve information from Vultr MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations are inherently Read category as they retrieve data without side effects. The absence of mutative language ('create', 'update', 'delete') and the search/filter nature of the function name support this classification. Low severity because searching plan information poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'search_plans_by_specs' indicates a query/search operation. No description provided, but naming convention strongly suggests retrieving or filtering plan information based on specifications without modification.
Documented attack patterns abuse exactly the kind of access search_plans_by_specs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Vultr MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_plans_by_specs:
{
"version": "1",
"default": "deny",
"tools": {
"search_plans_by_specs": {}
}
}search_plans_by_specs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_plans_by_specs. 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 search_plans_by_specs: 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.
search_plans_by_specs 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 search_plans_by_specs 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 search_plans_by_specs. 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.
search_plans_by_specs 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.
Start from Vultr MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
284 Vultr MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.