update_task
Change the schedule, destination, method, timeout, headers or body of an existing task. Omit a field to leave it unchanged — sending null is refused, because "unchanged" and "cleared" must not look the same. State is NOT editable here: use pause_task and resume_task.
This record as markdown: /tools/402cron/update-task.md
What update_task does on 402cron
AI agents use update_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.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Task id (UUID), as returned by create_task or list_tasks. |
url | string | — | The https:// destination. It must already be registered and verified — see register_destination. |
body | object | — | The body we send. Stored in the clear, so it must not carry credentials. A non-string is serialized as JSON. |
cron | string | — | 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 | — | Your name for the task. Unique among your live tasks; creating with an existing name updates it. |
method | string | — | HTTP method of the delivery. Default POST. GET and HEAD carry no body. |
headers | object | — | Headers we send with the delivery. Stored ENCRYPTED at rest — put credentials here, never in the body. |
timeoutMs | integer | — | 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.
Why update_task is rated Medium
An AI agent can call update_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 signalsAccepts URL/endpoint input (url) · Accepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs update_task 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 update_task, this is the rule to start with:
update_task 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 update_task call is checked against it from then on.
Questions about update_task
Change the schedule, destination, method, timeout, headers or body of an existing task. Omit a field to leave it unchanged — sending null is refused, because "unchanged" and "cleared" must not look the same. State is NOT editable here: use pause_task and resume_task. 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.
update_task accepts 8 parameters: id, url, body, cron, name, method, headers, timeoutMs. Required: id. 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 update_task: 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.
update_task 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 update_task 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 update_task. 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.
update_task 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