remove_pan_element
Remove element or folder from Private API Network
This record as markdown: /tools/delano-postman-mcp-server/remove-pan-element.md
What remove_pan_element does on Postman
AI agents call remove_pan_element 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 remove_pan_element is rated Critical
The tool permanently deletes elements or folders from the Private API Network. This is a destructive operation that cannot be easily undone—once removed, the structure and any associated configurations are gone.
From the tool's definition Tool name contains 'remove' and description states 'Remove element or folder from Private API Network', indicating irreversible deletion of API network resources.
Attacks that exploit this kind of access
The rule that runs remove_pan_element 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 remove_pan_element, this is the rule to start with:
remove_pan_element 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 remove_pan_element call is checked against it from then on.
Questions about remove_pan_element
Remove element or folder from Private API Network. 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 remove_pan_element: 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.
remove_pan_element 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 remove_pan_element 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 remove_pan_element. 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.
remove_pan_element 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