# create_task

Register a schedule against a destination you have already verified. Idempotent on "name": the same name updates the existing task instead of creating a second one. Creating costs nothing; each delivery ATTEMPT costs one credit.

Agent View of the PolicyLayer registry record for `create_task`. HTML page: https://policylayer.com/tools/402cron/create-task

## Facts

- Tool: `create_task`
- Server: 402cron (`https://402cron.com/mcp`) — https://policylayer.com/tools/402cron.md
- Homepage: https://github.com/402cron/402cron
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 7 (3 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `url` | string | yes | The https:// destination. It must already be registered and verified — see register_destination. |
| `body` | object | no | The body we send. Stored in the clear, so it must not carry credentials. A non-string is serialized as JSON. |
| `cron` | string | yes | 5 fields, UTC only, one minute at the finest. Operators: * a-b a,b */n a-b/n. Names: SUN-SAT (day), JAN-DEC (month). Macros: @yearly @annually @monthly @weekly |
| `name` | string | yes | Your name for the task. Unique among your live tasks; creating with an existing name updates it. |
| `method` | string | no | HTTP method of the delivery. Default POST. GET and HEAD carry no body. |
| `headers` | object | no | Headers we send with the delivery. Stored ENCRYPTED at rest — put credentials here, never in the body. |
| `timeoutMs` | integer | no | How long we wait for your server, 250-2000 ms. Answer 202 and do the work behind it. |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "create_task",
    "arguments": {
      "url": "<url>",
      "cron": "<cron>",
      "name": "<name>"
    }
  }
}
```

## Why create_task is rated Medium

An AI agent can call create_task faster than any human can review: one bad instruction and it creates or modifies resources in 402cron by the hundred, each call as confident as the last.

Risk signals: Accepts URL/endpoint input (url) · Accepts raw HTML/template content (body)

## Use case

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

## Recommended policy (PolicyLayer)

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

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

## Other tools on 402cron (15)

- `delete_destination` — Destructive — https://policylayer.com/tools/402cron/delete-destination.md
- `delete_task` — Destructive — https://policylayer.com/tools/402cron/delete-task.md
- `run_task_now` — Execute — https://policylayer.com/tools/402cron/run-task-now.md
- `get_docs` — Read — https://policylayer.com/tools/402cron/get-docs.md
- `get_pricing` — Read — https://policylayer.com/tools/402cron/get-pricing.md
- `get_service_status` — Read — https://policylayer.com/tools/402cron/get-service-status.md
- `get_task` — Read — https://policylayer.com/tools/402cron/get-task.md
- `list_destinations` — Read — https://policylayer.com/tools/402cron/list-destinations.md
- `list_tasks` — Read — https://policylayer.com/tools/402cron/list-tasks.md
- `pause_task` — Read — https://policylayer.com/tools/402cron/pause-task.md
- `verify_destination` — Read — https://policylayer.com/tools/402cron/verify-destination.md
- `register_destination` — Write — https://policylayer.com/tools/402cron/register-destination.md
- `restore_task` — Write — https://policylayer.com/tools/402cron/restore-task.md
- `resume_task` — Write — https://policylayer.com/tools/402cron/resume-task.md
- `update_task` — Write — https://policylayer.com/tools/402cron/update-task.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=402cron · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/402cron
