This record as markdown: /tools/delano-postman-mcp-server/create-api-schema.md
What create_api_schema does on Postman
AI agents use create_api_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 create_api_schema is rated Medium
This tool creates (writes) a new API schema in Postman, which is a reversible operation. It does not execute external code, delete data, or transfer funds. While schema creation could influence API testing workflows, the immediate action is data creation without side effects beyond the schema resource itself.
From the tool's definition Tool name 'create_api_schema' and description 'Create a schema for an API' indicate data creation. The verb 'create' modifies Postman's data model by adding a new schema resource.
Attacks that exploit this kind of access
The rule that runs create_api_schema safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Postman, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_api_schema, this is the rule to start with:
create_api_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Postman, apply this rule, and every create_api_schema call is checked against it from then on.
Questions about create_api_schema
Create a schema for an API. 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 create_api_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.
create_api_schema 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 create_api_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.
Set action: deny in the PolicyLayer policy for create_api_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.
create_api_schema is provided by the Postman MCP server (delano/postman-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Postman, and thousands of servers like it.
This server
Across the catalogue