Cancel a task. Changes status to CANCELED. Args: task_id: ID of the task to cancel Returns: Updated task data
AI agents use cancel_task to create or update resources in Taskdog — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Taskdog environment.
Cancelling a task changes its status to CANCELED, which is a reversible state modification (the task data still exists and could potentially be re-opened/un-cancelled). This is a Write operation rather than Destructive since it doesn't delete the task. Medium severity because an AI agent could cancel tasks that shouldn't be cancelled, disrupting workflows.
From the tool's definition Cancel a task. Changes status to CANCELED.
Documented attack patterns abuse exactly the kind of access cancel_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Taskdog, and nothing reaches the server without passing your rules. This is the rule we recommend for cancel_task:
{
"version": "1",
"default": "deny",
"tools": {
"cancel_task": {
"limits": [
{
"counter": "cancel_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}cancel_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.
Free to start. No card required.
Cancel a task. Changes status to CANCELED. Args: task_id: ID of the task to cancel Returns: Updated task data. It is categorised as a Write tool in the Taskdog MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Taskdog MCP server in PolicyLayer and add a rule for cancel_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 Taskdog. Nothing to install.
cancel_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 cancel_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 cancel_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.
cancel_task is provided by the Taskdog MCP server (kohei-wada/taskdog). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Taskdog, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 Taskdog tools catalogued and risk-classified — across an index of 43,000+ MCP servers.