http_delete
Send an HTTP DELETE request. Some REST APIs require a body with DELETE (e.g. bulk delete). body: optional request body. headers: extra request headers as 'Name: Value' pairs separated by newlines or semicolons. Returns status code and response body.
This record as markdown: /tools/aaronckj-mcp-nettools/http-delete.md
What http_delete does on Mcp Nettools
AI agents call http_delete to permanently remove resources in Mcp Nettools, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why http_delete is rated Critical
HTTP DELETE requests are used to remove resources on remote servers. While the actual destructiveness depends on the target endpoint, DELETE is semantically an irreversible operation — it deletes resources. The tool also supports bulk delete via an optional body, increasing the blast radius. This is classified as Destructive because DELETE requests typically cannot be undone once the server processes them.
From the tool's definition Send an HTTP DELETE request... Returns status code and response body.
Attacks that exploit this kind of access
The rule that runs http_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For http_delete, this is the rule to start with:
http_delete 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 Mcp Nettools, apply this rule, and every http_delete call is checked against it from then on.
Questions about http_delete
Send an HTTP DELETE request. Some REST APIs require a body with DELETE (e.g. bulk delete). body: optional request body. headers: extra request headers as 'Name: Value' pairs separated by newlines or semicolons. Returns status code and response body. It is categorised as a Destructive tool in the Mcp Nettools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Nettools 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 Mcp Nettools. 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 Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Nettools, and thousands of servers like it.
Across the catalogue