Update the status of a task. When closing a task (status=done), provide a detailed completionReport describing what was done: files modified with line numbers, tools called, memories written, and any other relevant detail.
AI agents use update_task_status to create or update resources in RoadBoard — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RoadBoard environment.
update_task_status modifies project state by changing task status values. This is a Write operation because: (1) it creates or modifies data (task status field), (2) the change is reversible (status can be updated again to a different value), and (3) it does not delete, destroy, or move money.
From the tool's definition Tool description explicitly states 'Update the status of a task' and accepts parameters to modify task state (status=done). This is a reversible modification operation: task status can be changed between states (e.g., done → in_progress).
Attacks that exploit this kind of access
Update the status of a task. When closing a task (status=done), provide a detailed completionReport describing what was done: files modified with line numbers, tools called, memories written, and any other relevant detail. It is categorised as a Write tool in the RoadBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RoadBoard MCP server in PolicyLayer and add a rule for update_task_status: 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 RoadBoard. Nothing to install.
update_task_status 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_status 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_status. 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_status is provided by the RoadBoard MCP server (maless88/roadboard). 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 →