Rename an existing section.
AI agents use update_section to create or update resources in Todoist MCP Helper — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist MCP Helper environment.
Renaming a section modifies metadata reversibly and is recoverable (can be renamed again). This is strictly a Write operation. Severity is medium because misuse could corrupt task organization or cause confusion across a team using shared sections, but the action itself is not destructive or irreversible.
From the tool's definition Tool performs 'Rename an existing section' – a reversible modification operation on task management data. Sibling tools show this server manages Todoist projects/sections/tasks; renaming is a standard write operation.
Attacks that exploit this kind of access
Rename an existing section. It is categorised as a Write tool in the Todoist MCP Helper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todoist MCP Helper MCP server in PolicyLayer and add a rule for update_section: 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 Todoist MCP Helper. Nothing to install.
update_section 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 update_section 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 update_section. 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.
update_section is provided by the Todoist MCP Helper MCP server (littlepeter52012/todoist-mcp-helper). 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 →