移动待办事项到列表开头或结尾
AI agents use move_todo to create or update resources in Code Analysis MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Code Analysis MCP Server environment.
This tool modifies the state of a todo item by changing its position within a list, which is a reversible operation characteristic of Write category. It does not delete data (Destructive), execute arbitrary code (Execute), create financial obligations (Financial), or retrieve data without side effects (Read). The blast radius is low as it only reorders existing items and does not affect critical operations.
From the tool's definition Tool name 'move_todo' and description '移动待办事项到列表开头或结尾' (move todo item to the beginning or end of the list) indicates reordering/modifying the position of an existing todo item in a list.
Attacks that exploit this kind of access
移动待办事项到列表开头或结尾. It is categorised as a Write tool in the Code Analysis MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Code Analysis MCP Server MCP server in PolicyLayer and add a rule for move_todo: 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 Code Analysis MCP Server. Nothing to install.
move_todo 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 move_todo 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 move_todo. 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.
move_todo is provided by the Code Analysis MCP Server MCP server (zeocax/code-mcp). 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 →