This record as markdown: /tools/delano-postman-mcp-server/delete-schema-file.md
What delete_schema_file does on Postman
AI agents call delete_schema_file to permanently remove resources in Postman, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_schema_file is rated Critical
Deletion operations cannot be undone and permanently remove data from the system. Within a Postman API management context, deleting a schema file removes a critical artifact that may be referenced by multiple APIs or collections. This action has a high blast radius if triggered unintentionally—schema dependencies could break and the file cannot be recovered.
From the tool's definition Tool name is 'delete_schema_file' and description states 'Delete a schema file'. The verb 'delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_schema_file 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 delete_schema_file, this is the rule to start with:
delete_schema_file is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Postman, apply this rule, and every delete_schema_file call is checked against it from then on.
Questions about delete_schema_file
Delete a schema file. It is categorised as a Destructive tool in the Postman MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Postman MCP server in PolicyLayer and add a rule for delete_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.
delete_schema_file is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_schema_file 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.
Across the catalogue