Update an existing task. Pass the version from get_tasks to detect conflicts.${noProjectsNote}
AI agents use update_task to create or update resources in Writbase — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Writbase environment.
This tool creates or modifies data in a reversible manner. Updates are characteristic of Write category—changes can be undone through subsequent updates. The severity is medium because task management updates in a fleet context could affect agent workflows, but the operation is not destructive (data remains recoverable) and not financial.
From the tool's definition Tool description states 'Update an existing task', which is a reversible modification operation. The reference to 'version from get_tasks to detect conflicts' confirms optimistic concurrency control typical of write operations.
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 Writbase, 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. Pass the version from get_tasks to detect conflicts.${noProjectsNote}. It is categorised as a Write tool in the Writbase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Writbase 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 Writbase. 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 Writbase MCP server (https://{PROJECT_REF}.supabase.co/functions/v1/mcp-server/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Writbase, 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.
13 Writbase tools catalogued and risk-classified — across an index of 43,000+ MCP servers.