Create a new section within a Todoist project to organize tasks. Sections help categorize and group related tasks within a project. You can optionally specify the order to control where the section appears in the project hierarchy. Returns the complete section object with all metadata upon succes...
AI agents use create_section to create or update resources in Todoist MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist MCP Server environment.
Creating a section is a Write operation because it adds new data to the system in a reversible manner. While the server provides destructive tools (delete_project, delete_section, delete_label, delete_comment), this specific tool only creates structural organization without deleting or permanently modifying existing data.
From the tool's definition Tool description explicitly states 'Create a new section' which is a reversible data modification operation. The tool creates organizational metadata (a section object) within a Todoist project.
Documented attack patterns abuse exactly the kind of access create_section gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Todoist MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_section:
{
"version": "1",
"default": "deny",
"tools": {
"create_section": {
"limits": [
{
"counter": "create_section_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_section stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new section within a Todoist project to organize tasks. Sections help categorize and group related tasks within a project. You can optionally specify the order to control where the section appears in the project hierarchy. Returns the complete section object with all metadata upon successful creation. It is categorised as a Write tool in the Todoist MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todoist MCP Server MCP server in PolicyLayer and add a rule for create_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 Server. Nothing to install.
create_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 create_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 create_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.
create_section is provided by the Todoist MCP Server MCP server (koki-develop/todoist-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Todoist MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
32 Todoist MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.