update_annotation

SERVERDoit SOURCE@doitintl/doit-mcp-server

Medium RISK CLASS

Category Write

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/update-annotation.md

WHAT IT DOES

What update_annotation does on Doit

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

Parameter	Type	Required	Description
`id`	string	Yes	The ID of the annotation to update (required).
`labels`	object	—	Replacement list of existing console label IDs. Omission or null leaves unchanged; [] clears all labels.
`content`	string	Yes	Required nonempty content on every update, even when only changing associations or timestamp.
`reports`	object	—	Replacement list of report IDs. Omission or null leaves unchanged; [] clears all report associations.
`timestamp`	object	—	RFC 3339 timestamp with seconds and Z or ±HH:MM timezone; fractional seconds are supported. Omit or set null to leave unchanged.

Parameters from the server's own tool schema.

RISK

Why update_annotation is rated Medium

An AI agent can call update_annotation faster than any human can review: one bad instruction and it creates or modifies resources in Doit by the hundred, each call as confident as the last.

Risk signalsAccepts raw HTML/template content (content) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_annotation safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_annotation, this is the rule to start with:

update_annotation Rate-limited

update_annotation 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": {
    "update_annotation": {
      "limits": [
        {
          "counter": "update_annotation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every update_annotation call is checked against it from then on.

FAQ

Questions about update_annotation

What does the update_annotation tool do? +

Use this when the user wants to modify an existing annotation. Nonempty content is required on every update. Omitted or null timestamp/reports/labels remain unchanged; reports and labels replace their lists, and [] clears them. Changes apply immediately. Do NOT use this for creating new annotations (use create_annotation) or labels (use update_label). It is categorised as a Write tool in the Doit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does update_annotation accept? +

update_annotation accepts 5 parameters: id, labels, content, reports, timestamp. Required: id, content. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_annotation? +

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

What risk level is update_annotation? +

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

Can I rate-limit update_annotation? +

Yes. Add a rate_limit block to the update_annotation 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 update_annotation completely? +

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

update_annotation is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Doit, and thousands of servers like it.

This server

All 238 Doit tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →