List service collections for a specific project.
AI agents call list_collections_by_project 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.
This is a straightforward read operation that retrieves and displays existing collection metadata. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. The blast radius of misuse is minimal—an agent could only enumerate collections, which represents information disclosure but no operational impact.
From the tool's definition Tool name 'list_collections_by_project' and description 'List service collections for a specific project' indicate a retrieval operation that queries project collections without modifying, deleting, or executing actions.
Documented attack patterns abuse exactly the kind of access list_collections_by_project 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 list_collections_by_project:
{
"version": "1",
"default": "deny",
"tools": {
"list_collections_by_project": {}
}
}list_collections_by_project 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.
List service collections for a specific project. 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_collections_by_project: 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_collections_by_project 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_collections_by_project 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_collections_by_project. 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_collections_by_project 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.