Re-enable a previously paused task and recompute the next run time.
AI agents use resume_task to create or update resources in Schedule Task MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Schedule Task MCP environment.
resume_task modifies the state of an existing task by re-enabling it and recalculating its schedule. This is a reversible state change (the task can be paused again), making it a Write operation. The medium severity reflects that resuming a task could trigger automated AI agent invocations on a schedule, which may have downstream effects depending on what the task does.
From the tool's definition Re-enable a previously paused task and recompute the next run time
Attacks that exploit this kind of access
Re-enable a previously paused task and recompute the next run time. It is categorised as a Write tool in the Schedule Task MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Schedule Task 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 Schedule Task MCP. 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 Schedule Task MCP server (liao1fan/schedule-task-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →