AI agents call list_collections to retrieve information from Postman without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing collections without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal security risk, as it only exposes information about collections already accessible within the workspace.
From the tool's definition Tool name is 'list_collections' and description states 'List all collections in a workspace' — this is a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access list_collections gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postman, and nothing reaches the server without passing your rules. This is the rule we recommend for list_collections:
{
"version": "1",
"default": "deny",
"tools": {
"list_collections": {}
}
}list_collections 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 all collections in a workspace. 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 (salehkhatri/postman-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Postman tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 Postman tools catalogued and risk-classified — across an index of 42,500+ MCP servers.