resume_task
Start firing again on the schedule. Refused if your balance is empty — buy deliveries first.
This record as markdown: /tools/402cron/resume-task.md
What resume_task does on 402cron
AI agents use resume_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. |
Parameters from the server's own tool schema.
Why resume_task is rated Medium
An AI agent can call resume_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.
Attacks that exploit this kind of access
The rule that runs resume_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 resume_task, this is the rule to start with:
resume_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 resume_task call is checked against it from then on.
Questions about resume_task
Start firing again on the schedule. Refused if your balance is empty — buy deliveries first. 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.
resume_task accepts 1 parameter: id. 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 resume_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.
resume_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 resume_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 resume_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.
resume_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