Manages todos. Per-action usage: • nextId — Returns the next available todo ID. No extra params needed. • create — Creates a new todo file. Required: title (string), description (1-2 sentence problem statement), priority ("p0"|"p1"|"p2"|"p3"), criteria (string array of acceptance criteria). Optio...
AI agents use call_tool_todo_manager to create or update resources in Superkit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Superkit environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
force | boolean | — | Bypass terminal-state or unchecked-criteria guards. Used by: start, done, complete. |
title | string | — | Todo title. Used by: create. |
action | string | Yes | |
todoId | string | — | RELATIVE PATH to the todo file from projectPath, e.g. 'todos/001-pending-p2-my-task.md'. NOT just the numeric ID. Used by: start, done, complete. |
criteria | array | — | Acceptance criteria checklist items. Used by: create. |
priority | string | — | Priority level. p0=critical, p1=urgent, p2=normal, p3=low. Used by: create. |
description | string | — | 1-2 sentence problem statement. Used by: create. |
projectPath | string | Yes |
Parameters from the server's own tool schema.
The tool creates and modifies todo files (creating new files, updating status to in-progress). These are reversible write operations with no code execution, financial impact, or irreversible destruction. Severity is medium because an AI agent could create many spurious todos or alter task states, but the blast radius is limited to project management files.
From the tool's definition 'create — Creates a new todo file', 'start — Marks a todo as in-progress'
Attacks that exploit this kind of access
Manages todos. Per-action usage: • nextId — Returns the next available todo ID. No extra params needed. • create — Creates a new todo file. Required: title (string), description (1-2 sentence problem statement), priority ("p0"|"p1"|"p2"|"p3"), criteria (string array of acceptance criteria). Optional: projectPath. Example: { action: "create", title: "Add auth", description: "Implement JWT login.", priority: "p2", criteria: ["User can log in", "Token is stored"], projectPath: "." } • start — Marks a todo as in-progress. Required: todoId = RELATIVE PATH to the todo file, e.g. "todos/001-pending-p2-my-task.md". The file must exist at that path relative to projectPath. Example: { action: "start", todoId: "todos/001-pending-p2-my-task.md", projectPath: "." } • done — Marks a todo as done. Required: todoId = relative path (same format as start). All acceptance criteria checkboxes must be checked, or pass force: true to bypass. Example: { action: "done", todoId: "todos/001-in-progress-p2-my-task.md", force: true, projectPath: "." } • complete — Marks a todo as complete (final state). Required: todoId = relative path (same format as start/done). Example: { action: "complete", todoId: "todos/001-done-p2-my-task.md", force: true, projectPath: "." } ⚠️ IMPORTANT: todoId must be the FULL RELATIVE FILE PATH (e.g. "todos/001-in-progress-p2-my-task.md"), NOT just the numeric ID ("001"). The filename changes with each status transition, so always use the current filename on disk. It is categorised as a Write tool in the Superkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
call_tool_todo_manager accepts 8 parameters: force, title, action, todoId, criteria, priority, description, projectPath. Required: action, projectPath. The full parameter table on this page comes from the server's own tool schema.
Register the Superkit MCP server in PolicyLayer and add a rule for call_tool_todo_manager: 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 Superkit. Nothing to install.
call_tool_todo_manager 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 call_tool_todo_manager 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 call_tool_todo_manager. 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.
call_tool_todo_manager is provided by the Superkit MCP server (superkit-mcp-server). 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 →