# curl_post

Make an HTTP POST request using curl

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

## Facts

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

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

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

## Why curl_post is rated Medium

HTTP POST is the standard method for creating resources or submitting data. It can write data to arbitrary external services/APIs. The blast radius is high because an AI agent could POST sensitive data, trigger external workflows, or interact with any web endpoint reachable from the host. It is Write rather than Execute because POST itself is a data-submission operation, though misuse potential is significant.

From the tool's own definition: "'Make an HTTP POST request using curl' — POST requests create or submit data to external endpoints"

## Use case

AI agents use curl_post to create or update resources in Curl MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Curl MCP Server environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "curl_post": {
      "limits": [
        {
          "counter": "curl_post_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Curl MCP Server (5)

- `curl_delete` — Destructive — https://policylayer.com/tools/247arjun-mcp-curl/curl-delete.md
- `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_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