todoist_project_move_to_parent

WHAT IT DOES

What todoist_project_move_to_parent does on Mcp Todoist

AI agents use todoist_project_move_to_parent to create or update resources in Mcp Todoist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Todoist environment.

WHY IT NEEDS A POLICY

Why todoist_project_move_to_parent needs a policy

The tool modifies project hierarchy by changing parent-child relationships, which is a reversible write operation. It does not delete data (would be Destructive), does not execute arbitrary code (would be Execute), and does not involve financial transactions. The medium severity reflects that misuse could disrupt project organization and workflow, but the change is reversible through moving the project again.

From the tool's definition Tool name contains 'move' and description states 'Move a project under another project...or to root level.' This is a data modification operation that reorganizes project structure.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

todoist_project_move_to_parent Rate-limited

todoist_project_move_to_parent 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "todoist_project_move_to_parent": {
      "limits": [
        {
          "counter": "todoist_project_move_to_parent_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Todoist, so you can run agents against it safely.

FAQ

Questions about todoist_project_move_to_parent

What does the todoist_project_move_to_parent tool do? +

Move a project under another project (making it a sub-project) or to root level. Useful for organizing project hierarchies. It is categorised as a Write tool in the Mcp Todoist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on todoist_project_move_to_parent? +

Register the Mcp Todoist MCP server in PolicyLayer and add a rule for todoist_project_move_to_parent: 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 Mcp Todoist. Nothing to install.

What risk level is todoist_project_move_to_parent? +

todoist_project_move_to_parent is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit todoist_project_move_to_parent? +

Yes. Add a rate_limit block to the todoist_project_move_to_parent 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.

How do I block todoist_project_move_to_parent completely? +

Set action: deny in the PolicyLayer policy for todoist_project_move_to_parent. 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.

What MCP server provides todoist_project_move_to_parent? +

todoist_project_move_to_parent is provided by the Mcp Todoist MCP server (@greirson/mcp-todoist). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.