sync_collection_with_schema · Postman MCP: Risk & Policy

WHAT IT DOES

What sync_collection_with_schema does on Postman

AI agents use sync_collection_with_schema 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.

WHY IT NEEDS A POLICY

Why sync_collection_with_schema needs a policy

Syncing a collection with its schema modifies the collection by updating it to conform to the schema definition. This is a Write operation as it overwrites existing collection data, though it is likely reversible. The blast radius is medium since it could overwrite customizations or manual edits to the collection.

From the tool's definition 'Sync a collection with its schema' — synchronization overwrites/updates collection contents to match the schema

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sync_collection_with_schema Rate-limited

sync_collection_with_schema stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync_collection_with_schema": {
      "limits": [
        {
          "counter": "sync_collection_with_schema_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Postman, so you can run agents against it safely.

FAQ

Questions about sync_collection_with_schema

What does the sync_collection_with_schema tool do? +

Sync a collection with its schema. 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.

How do I enforce a policy on sync_collection_with_schema? +

Register the Postman MCP server in PolicyLayer and add a rule for sync_collection_with_schema: 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.

What risk level is sync_collection_with_schema? +

sync_collection_with_schema is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sync_collection_with_schema? +

Yes. Add a rate_limit block to the sync_collection_with_schema 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.

How do I block sync_collection_with_schema completely? +

Set action: deny in the PolicyLayer policy for sync_collection_with_schema. 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.

What MCP server provides sync_collection_with_schema? +

sync_collection_with_schema 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.

// THE FULL RECORD

sync_collection_with_schema is one line of Postman's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →