complete_task_by_name · Todoist MCP Helper MCP

WHAT IT DOES

What complete_task_by_name does on Todoist MCP Helper

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

WHY IT NEEDS A POLICY

Why complete_task_by_name needs a policy

Completing a task is a reversible modification (tasks can be uncompleted in Todoist). It does not create, execute external code, delete, or move money. However, it affects task state and uses partial name matching which introduces risk of completing the wrong task if multiple tasks have similar names.

From the tool's definition Tool performs 'complete_task_by_name' - marks a task as complete/done, which modifies the state of a task in Todoist. The description states it 'Complete[s] a task', indicating state modification rather than deletion or creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

complete_task_by_name Rate-limited

complete_task_by_name 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": {
    "complete_task_by_name": {
      "limits": [
        {
          "counter": "complete_task_by_name_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 Helper, so you can run agents against it safely.

FAQ

Questions about complete_task_by_name

What does the complete_task_by_name tool do? +

Complete a task by searching for it by name. Uses partial name matching. It is categorised as a Write tool in the Todoist MCP Helper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on complete_task_by_name? +

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

What risk level is complete_task_by_name? +

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

Can I rate-limit complete_task_by_name? +

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

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

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