Add a section to a project in Todoist
AI agents use add-section to create or update resources in Todoist MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist MCP environment.
The tool creates new data (a section) within a Todoist project, which is a write operation. It is not destructive (sections can be deleted), not financial, and not an execute operation that runs arbitrary code. Severity is medium because misconfigured sections could clutter a project structure, but the impact is limited and reversible through the sibling 'delete-section' tool.
From the tool's definition Tool name 'add-section' and description 'Add a section to a project in Todoist' indicate creation of a new organizational structure within a project. This is a reversible modification operation.
Attacks that exploit this kind of access
Add a section to a project in Todoist. It is categorised as a Write tool in the Todoist MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todoist MCP server in PolicyLayer and add a rule for add-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. Nothing to install.
add-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 add-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 add-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.
add-section is provided by the Todoist MCP server (jdh747/todoist-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 →