list_collections
List all collections in a workspace. Supports filtering and pagination.
This record as markdown: /tools/delano-postman-mcp-server/list-collections.md
What list_collections does on Postman
AI agents call list_collections to retrieve information from Postman 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 is rated Low
This tool retrieves and queries existing collections metadata without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal security impact—at most it could expose the names and structure of collections in a workspace, but causes no state changes.
From the tool's definition Tool name 'list_collections' and description 'List all collections in a workspace. Supports filtering and pagination.' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_collections safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postman, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_collections, this is the rule to start with:
list_collections 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 Postman, apply this rule, and every list_collections call is checked against it from then on.
Questions about list_collections
List all collections in a workspace. Supports filtering and pagination. It is categorised as a Read tool in the Postman MCP Server, which means it retrieves data without modifying state.
Register the Postman MCP server in PolicyLayer and add a rule for list_collections: 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 Postman. Nothing to install.
list_collections 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 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. 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 is provided by the Postman MCP server (delano/postman-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postman, and thousands of servers like it.
This server
Across the catalogue