list_collections_by_project

What list_collections_by_project does on Vultr MCP

AI agents call list_collections_by_project 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_collections_by_project is rated Low

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.

The rule that runs list_collections_by_project 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_collections_by_project, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_collections_by_project": {}
  }
}

Questions about list_collections_by_project