add_task_update · Dooist MCP: Risk & Policy

WHAT IT DOES

What add_task_update does on Dooist

AI agents use add_task_update to create or update resources in Dooist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dooist environment.

WHY IT NEEDS A POLICY

Why add_task_update needs a policy

The tool adds updates to task records, which is a create operation on task metadata. This is reversible (updates can be edited or removed) and has no destructive or executable side effects. It falls squarely into Write category rather than Read (it modifies data) or Execute (it doesn't run code or external commands).

From the tool's definition Tool description states 'Add a timestamped status update to a task', which creates new data (status updates) reversibly. This is a write operation that modifies task state without deletion or code execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_task_update Rate-limited

add_task_update 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_task_update": {
      "limits": [
        {
          "counter": "add_task_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dooist, so you can run agents against it safely.

FAQ

Questions about add_task_update

What does the add_task_update tool do? +

Add a timestamped status update to a task. Use this to track progress and activity on a task over time. It is categorised as a Write tool in the Dooist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_task_update? +

Register the Dooist MCP server in PolicyLayer and add a rule for add_task_update: 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 Dooist. Nothing to install.

What risk level is add_task_update? +

add_task_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_task_update? +

Yes. Add a rate_limit block to the add_task_update 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.

How do I block add_task_update completely? +

Set action: deny in the PolicyLayer policy for add_task_update. 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.

What MCP server provides add_task_update? +

add_task_update is provided by the Dooist MCP server (papermoose/dooist). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.