# curl_delete

Make an HTTP DELETE request using curl

Agent View of the PolicyLayer registry record for `curl_delete`. HTML page: https://policylayer.com/tools/247arjun-mcp-curl/curl-delete

## Facts

- Tool: `curl_delete`
- Server: Curl MCP Server (`247arjun/mcp-curl`) — https://policylayer.com/tools/247arjun-mcp-curl.md
- Homepage: https://github.com/247arjun/mcp-curl
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "curl_delete",
    "arguments": {}
  }
}
```

## Why curl_delete is rated Critical

HTTP DELETE requests are inherently destructive operations that remove data from remote systems. While the actual impact depends on what server endpoint is targeted, the tool's explicit purpose is to delete resources. Combined with the curl capability to target arbitrary URLs, this tool could irreversibly delete data on any accessible HTTP service.

From the tool's own definition: "Tool name is 'curl_delete' and description states 'Make an HTTP DELETE request using curl'. HTTP DELETE requests are designed to delete resources on remote servers."

## Use case

AI agents call curl_delete to permanently remove resources in Curl MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Curl MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "curl_delete"
  ]
}
```

## Other tools on Curl MCP Server (5)

- `curl_advanced` — Execute — https://policylayer.com/tools/247arjun-mcp-curl/curl-advanced.md
- `curl_download` — Read — https://policylayer.com/tools/247arjun-mcp-curl/curl-download.md
- `curl_get` — Read — https://policylayer.com/tools/247arjun-mcp-curl/curl-get.md
- `curl_post` — Write — https://policylayer.com/tools/247arjun-mcp-curl/curl-post.md
- `curl_put` — Write — https://policylayer.com/tools/247arjun-mcp-curl/curl-put.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=247arjun-mcp-curl · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/247arjun-mcp-curl