Make a DELETE request (convenience method).
AI agents call http_delete to permanently remove resources in Http Client — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
HTTP DELETE requests are designed to delete resources on remote servers. When an AI agent calls this tool with an arbitrary URL, it can irreversibly remove data or resources without undo capability. This is inherently destructive. While the actual destructiveness depends on what the target server implements, the tool's explicit purpose is deletion, placing it in the Destructive category (more severe than Execute).
From the tool's definition Tool name is 'http_delete' and description states 'Make a DELETE request (convenience method)'. DELETE is the HTTP method used to request deletion of a resource on a server.
Attacks that exploit this kind of access
Make a DELETE request (convenience method). It is categorised as a Destructive tool in the Http Client MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Http Client MCP server in PolicyLayer and add a rule for http_delete: 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 Http Client. Nothing to install.
http_delete 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 http_delete 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 http_delete. 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.
http_delete is provided by the Http Client MCP server (keijeizei/http-client-mcp). 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 →