AI agents call http_delete to permanently remove resources in MCP-RQuest — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
HTTP DELETE is a destructive verb that removes resources. While the outcome depends on what the target server implements, the explicit purpose and convention of DELETE is irreversible removal. The server's anti-bot bypassing amplifies risk by enabling unauthorized deletions at scale. This is more severe than Write (which is reversible) and qualifies as Destructive.
From the tool's definition Tool name 'http_delete' and description 'Make an HTTP DELETE request to the specified URL' directly enable DELETE operations. HTTP DELETE conventionally removes resources on the target server.
Documented attack patterns abuse exactly the kind of access http_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-RQuest, and nothing reaches the server without passing your rules. This is the rule we recommend for http_delete:
{
"version": "1",
"default": "deny",
"hide": [
"http_delete"
]
}http_delete 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.
Make an HTTP DELETE request to the specified URL. It is categorised as a Destructive tool in the MCP-RQuest MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP-RQuest 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-RQuest. 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-RQuest MCP server (xxxbrian/mcp-rquest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 MCP-RQuest tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
12 MCP-RQuest tools catalogued and risk-classified — across an index of 42,500+ MCP servers.