AI agents call delete_request 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.
The tool removes a request permanently from a collection without the ability to undo the action through the tool itself. This is irreversible data loss, fitting the Destructive category. Severity is high because inadvertent deletion of requests could disrupt workflows, testing suites, or shared collections, though the blast radius is limited to request metadata rather than production systems.
From the tool's definition Tool name is 'delete_request' and description states 'Delete a request from a collection' — the verb 'delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postman, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_request:
{
"version": "1",
"default": "deny",
"hide": [
"delete_request"
]
}delete_request disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a request from a collection. 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_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. 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 (salehkhatri/postman-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 Postman tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
19 Postman tools catalogued and risk-classified — across an index of 42,500+ MCP servers.