Update an existing task. Modify the properties of an existing task.
AI agents use updateTask to create or update resources in Teamwork MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Teamwork MCP environment.
This tool creates or modifies data reversibly by updating task properties. It does not delete data (which would be Destructive) or execute arbitrary code (which would be Execute). Updates to task properties can be reverted by subsequent updates, making this a Write operation.
From the tool's definition Tool name 'updateTask' and description 'Update an existing task. Modify the properties of an existing task.' indicate data modification.
Documented attack patterns abuse exactly the kind of access updateTask gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Teamwork MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for updateTask:
{
"version": "1",
"default": "deny",
"tools": {
"updateTask": {
"limits": [
{
"counter": "updatetask_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}updateTask 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. Modify the properties of an existing task. It is categorised as a Write tool in the Teamwork MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Teamwork MCP server in PolicyLayer and add a rule for updateTask: 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 Teamwork MCP. Nothing to install.
updateTask 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 updateTask 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 updateTask. 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.
updateTask is provided by the Teamwork MCP server (vizioz/teamwork-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Teamwork MCP, 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.
36 Teamwork MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.