Updates the status and/or other properties of one or more tasks. Must use this tool before executing tasks, and when finished executing tasks. Should always include lessons learned to inform future tasks. Important: Always update multiple tasks in a single call if dependencies allow it.
AI agents use update_task to create or update resources in Mcp Task Manager — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Task Manager environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tasks | array | Yes | The tasks to update |
Parameters from the server's own tool schema.
This tool creates or modifies task data (status, properties, lessons learned) without permanently deleting or destroying records. It is explicitly Write category: reversible data modification. Severity is medium because an agent could maliciously update many tasks incorrectly, but the effects are recoverable by reverting the changes. Confidence is high due to explicit 'Updates' language in the description.
From the tool's definition Tool description states 'Updates the status and/or other properties of one or more tasks.' Updates are reversible modifications to task data.
Risk signalsHigh parameter count (21 properties)
Attacks that exploit this kind of access
Updates the status and/or other properties of one or more tasks. Must use this tool before executing tasks, and when finished executing tasks. Should always include lessons learned to inform future tasks. Important: Always update multiple tasks in a single call if dependencies allow it. It is categorised as a Write tool in the Mcp Task Manager MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_task accepts 1 parameter: tasks. Required: tasks. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Task Manager 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 Mcp Task Manager. 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 Mcp Task Manager MCP server (@blizzy/mcp-task-manager). 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 →