archive_project · Todoist MCP Server MCP: Risk & Policy

WHAT IT DOES

What archive_project does on Todoist MCP Server

AI agents use archive_project 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.

WHY IT NEEDS A POLICY

Why archive_project needs a policy

Archiving projects modifies their status/visibility but does not irreversibly delete them—users can typically unarchive projects to restore them. This places it in the Write category (reversible data modification) rather than Destructive. The severity is medium because an AI agent misusing this tool could remove multiple projects from active view, causing workflow disruption, but the action is recoverable.

From the tool's definition The tool is named 'archive_project' and described as 'Archive a project'. Archiving is a reversible operation that modifies project state without permanently deleting data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_project Rate-limited

archive_project 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": {
    "archive_project": {
      "limits": [
        {
          "counter": "archive_project_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 Todoist MCP Server, so you can run agents against it safely.

FAQ

Questions about archive_project

What does the archive_project tool do? +

Archive a project. 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.

How do I enforce a policy on archive_project? +

Register the Todoist MCP Server MCP server in PolicyLayer and add a rule for archive_project: 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.

What risk level is archive_project? +

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

Can I rate-limit archive_project? +

Yes. Add a rate_limit block to the archive_project 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 archive_project completely? +

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

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