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. V...
This record as markdown: /tools/402cron/register-destination.md
What register_destination does on 402cron
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | The https:// URL you control. |
Parameters from the server's own tool schema.
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 signalsAccepts URL/endpoint input (url) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs register_destination safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 402cron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For register_destination, this is the rule to start with:
register_destination stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 402cron, apply this rule, and every register_destination call is checked against it from then on.
Questions about 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. It is categorised as a Write tool in the 402cron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
register_destination accepts 1 parameter: url. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the 402cron MCP server in PolicyLayer and add a rule for register_destination: 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 402cron. Nothing to install.
register_destination is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the register_destination 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 register_destination. 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.
register_destination is provided by the 402cron MCP server (https://402cron.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 402cron, and thousands of servers like it.
This server
Across the catalogue