Disable future runs without deleting the task. Ideal for vacations, maintenance windows, or temporary shutdowns.
AI agents use pause_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.
pause_task modifies task state (enabled→disabled) reversibly, fitting the Write category (modifies data reversibly). It is not Destructive because the task and its history persist, not deleted. It is not Execute because it doesn't trigger external operations or code execution—it only changes a boolean flag.
From the tool's definition Tool description states 'Disable future runs without deleting the task' — this is a state modification that reverses (task can be resumed via sibling resume_task).
Attacks that exploit this kind of access
Disable future runs without deleting the task. Ideal for vacations, maintenance windows, or temporary shutdowns. 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 pause_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.
pause_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 pause_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 pause_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.
pause_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 →