Sync TodoWrite updates to PLAN.md checkboxes - TodoWrite integration for automatic checkbox updates
AI agents use sync_todo_checkboxes to create or update resources in Agent Communication MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Communication MCP Server environment.
This tool creates or modifies data (checkbox states in a markdown file) in a reversible manner. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). The 'medium' severity reflects that erroneous checkbox updates could cause confusion in task tracking but remain reversible and have limited blast radius compared to file deletion or code execution.
From the tool's definition Tool performs 'Sync TodoWrite updates to PLAN.md checkboxes' - explicitly modifies files by updating checkbox states in PLAN.md. The description uses 'integration for automatic checkbox updates' indicating reversible state changes to tracked data.
Attacks that exploit this kind of access
Sync TodoWrite updates to PLAN.md checkboxes - TodoWrite integration for automatic checkbox updates. It is categorised as a Write tool in the Agent Communication MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Communication MCP Server MCP server in PolicyLayer and add a rule for sync_todo_checkboxes: 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 Agent Communication MCP Server. Nothing to install.
sync_todo_checkboxes 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 sync_todo_checkboxes 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 sync_todo_checkboxes. 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.
sync_todo_checkboxes is provided by the Agent Communication MCP Server MCP server (jerfowler/agent-comm-mcp-server). 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 →