Update an existing task. Args: task_id: ID of the task to update name: New task name priority: New priority deadline: New deadline in ISO format with time (e.g., '2025-12-11T18:00:00') estimated_duration: New estimated duration in hours (e.g., 0.5 = 30min, 1.5 = 1h30m) tags: New tags list (replac...
AI agents use update_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.
This tool modifies existing task records (name, priority, deadline, duration, tags, status fields, scheduling data) without deleting or executing external operations. Updates are reversible—prior values can be restored by re-updating.
From the tool's definition Tool description explicitly states 'Update an existing task' with parameters that modify task properties: name, priority, deadline, estimated_duration, tags, is_fixed, planned_start, planned_end. These are reversible modifications to task data.
Documented attack patterns abuse exactly the kind of access update_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 update_task:
{
"version": "1",
"default": "deny",
"tools": {
"update_task": {
"limits": [
{
"counter": "update_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Update an existing task. Args: task_id: ID of the task to update name: New task name priority: New priority deadline: New deadline in ISO format with time (e.g., '2025-12-11T18:00:00') estimated_duration: New estimated duration in hours (e.g., 0.5 = 30min, 1.5 = 1h30m) tags: New tags list (replaces existing) is_fixed: New fixed status planned_start: New planned start datetime in ISO format (e.g., '2025-12-11T09:00:00') planned_end: New planned end datetime in ISO format (e.g., '2025-12-11T17:00:00') 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 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 Taskdog. 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 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.