create_update_schema_file · Postman MCP: Risk & Policy

WHAT IT DOES

What create_update_schema_file does on Postman

AI agents use create_update_schema_file 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 create_update_schema_file needs a policy

This tool creates new schema files or modifies existing ones, which are reversible operations. It does not delete, execute code, move funds, or retrieve data without side effects. The blast radius is medium because corrupted or malicious schema files could affect API validation and testing workflows, but the operation is reversible through further updates or deletions.

From the tool's definition Tool name 'create_update_schema_file' and description 'Create or update a schema file' explicitly indicate both creation and modification operations. The word 'create' and 'update' denote reversible write operations on schema file artifacts.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_update_schema_file Rate-limited

create_update_schema_file 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": {
    "create_update_schema_file": {
      "limits": [
        {
          "counter": "create_update_schema_file_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 create_update_schema_file

What does the create_update_schema_file tool do? +

Create or update a schema file. 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 create_update_schema_file? +

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

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

Can I rate-limit create_update_schema_file? +

Yes. Add a rate_limit block to the create_update_schema_file 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 create_update_schema_file completely? +

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

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