# register_destination

Claim an https:// URL you control. We answer with a challenge and a SIGNING SECRET that is shown ONCE and never again — store it before you do anything else; it is what lets you verify that a delivery really came from us. The permission covers that path and everything beneath it, nothing above. Verification is one request from us to the exact URL you registered: POST, headers X-402cron-Challenge: <value> and X-402cron-Event: verify, JSON body {"challenge":"<value>"}. Reply within 5 seconds, without a redirect, with a body that is the bare value or {"challenge":"<value>"}; we read the first 512 bytes and do not check the HTTP status (2xx is fine). Then call POST /api/destinations/{id}/verify within 15 minutes of registering. A fixed-response webhook cannot pass: you need an endpoint you can program. Registering a URL that is still pending issues a new challenge and a new signing secret every time — the old secret immediately stops verifying deliveries; a verified URL is left untouched unless you add ?rotate=1. The daily verification allowance (10 per destination, 40 per client, UTC day) does not reset on re-registration.

Agent View of the PolicyLayer registry record for `register_destination`. HTML page: https://policylayer.com/tools/402cron/register-destination

## Facts

- Tool: `register_destination`
- 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: 1 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `url` | string | yes | The https:// URL you control. |

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": "register_destination",
    "arguments": {
      "url": "<url>"
    }
  }
}
```

## Why register_destination is rated Medium

An AI agent can call register_destination 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) · Bulk/mass operation — affects multiple targets

## Use case

AI agents use register_destination 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": {
    "register_destination": {
      "limits": [
        {
          "counter": "register_destination_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
- `create_task` — Write — https://policylayer.com/tools/402cron/create-task.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
