Delete an API request from a Postman collection
AI agents call delete_request to permanently remove resources in Postman MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations are irreversible and cannot be undone, placing this tool in the Destructive category. While the blast radius is limited to Postman collection metadata rather than production systems, accidental deletion of API request definitions could disrupt workflows and require manual recovery.
From the tool's definition Tool name is 'delete_request' and description states 'Delete an API request from a Postman collection'. The verb 'Delete' combined with removal of data from a collection indicates irreversible deletion.
Attacks that exploit this kind of access
Delete an API request from a Postman collection. It is categorised as a Destructive tool in the Postman MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Postman MCP Server MCP server in PolicyLayer and add a rule for delete_request: 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 MCP Server. Nothing to install.
delete_request 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_request 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_request. 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_request is provided by the Postman MCP Server MCP server (sondang91/postman-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →