Update an existing task. Only provided fields will be changed. Args: - id_task (string, required): Task ID to update - title (string, optional): New task name - email_user_to (string, optional): New assignee email - text (string, optional): New description - priority (string, optional): New prior...
AI agents use worksection_update_task to create or update resources in Worksection MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Worksection MCP Server environment.
This tool creates or modifies data reversibly. It updates task attributes within the Worksection project management platform but does not delete, destroy, or execute external code. The changes are reversible through subsequent updates. While it affects task metadata and could impact project planning (affecting budget and timeline estimates), it remains a Write operation.
From the tool's definition Tool description states 'Update an existing task. Only provided fields will be changed.' The arguments allow modification of task properties (title, description, priority, dates, estimates, budget) without deletion or destruction.
Attacks that exploit this kind of access
Update an existing task. Only provided fields will be changed. Args: - id_task (string, required): Task ID to update - title (string, optional): New task name - email_user_to (string, optional): New assignee email - text (string, optional): New description - priority (string, optional): New priority 0-10 - date_start (string, optional): New start date YYYY-MM-DD - date_end (string, optional): New due date YYYY-MM-DD - max_time (string, optional): New time estimate - max_money (string, optional): New budget Returns: Updated task data. It is categorised as a Write tool in the Worksection MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Worksection MCP Server MCP server in PolicyLayer and add a rule for worksection_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 Worksection MCP Server. Nothing to install.
worksection_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 worksection_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 worksection_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.
worksection_update_task is provided by the Worksection MCP Server MCP server (novgorodskii/worksection-mcp-server). 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 →