AI agents use fork_collection to create or update resources in Postman — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Postman environment.
Forking a collection creates a new copy/branch of an existing collection in a target workspace. This is a reversible write operation — it creates new data but does not delete or overwrite existing data. It is analogous to a copy or create operation, placing it in the Write category.
From the tool's definition Fork a collection to a workspace
Attacks that exploit this kind of access
Fork a collection to a workspace. It is categorised as a Write tool in the Postman MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Postman MCP server in PolicyLayer and add a rule for fork_collection: 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.
fork_collection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the fork_collection 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 fork_collection. 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.
fork_collection 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 →