todo_write
AI agents use todo_write to create or update resources in MCP Claude Code — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Claude Code environment.
The name 'todo_write' most naturally denotes creating or modifying TODO entries or files, which is a Write operation (reversible data modification). While the empty description prevents certainty, the server's documented ability to 'modify files' and the pattern of sibling write-oriented tools (edit, content_replace, multi_edit) support this classification.
From the tool's definition Tool name 'todo_write' implies creating or modifying a TODO list/file. Server context describes 'modify files' and 'direct file system interactions', and sibling tools include 'edit' and 'multi_edit', which are Write operations.
Attacks that exploit this kind of access
todo_write. It is categorised as a Write tool in the MCP Claude Code MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Claude Code MCP server in PolicyLayer and add a rule for todo_write: 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 MCP Claude Code. Nothing to install.
todo_write 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 todo_write 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 todo_write. 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.
todo_write is provided by the MCP Claude Code MCP server (sdglbl/mcp-claude-code). 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 →