AI agents call list_collection_access_keys 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 or enumerates existing access keys associated with collections. It retrieves information without creating, modifying, deleting, or executing anything. Although access keys are sensitive credentials, the tool itself only reads/lists them; the risk of exposure depends on downstream misuse by the agent, not the tool's inherent capability. Severity is low because listing is a passive query operation.
From the tool's definition Tool name contains 'list' and description states 'List collection access keys' with optional filtering—a retrieval operation with no side effects.
Attacks that exploit this kind of access
List collection access keys with optional filtering by collection ID. 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_collection_access_keys: 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_collection_access_keys 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_collection_access_keys 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_collection_access_keys. 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_collection_access_keys is provided by the Postman MCP server (postmanv3/postman-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →