update_task_by_name · Todoist MCP Helper MCP: Risk & Policy

WHAT IT DOES

What update_task_by_name does on Todoist MCP Helper

AI agents use update_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 update_task_by_name needs a policy

The tool name clearly indicates it updates task data by name, which is a reversible modification operation (Write category). Severity is medium because task updates are non-destructive but could impact productivity workflows if misused at scale. Confidence is high because the name unambiguously indicates a modification action, despite empty description.

From the tool's definition Tool name is 'update_task_by_name' and operates within Todoist task management system. Server context shows sibling tools that create, delete, and close tasks, indicating this modifies task data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_task_by_name Rate-limited

update_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": {
    "update_task_by_name": {
      "limits": [
        {
          "counter": "update_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 update_task_by_name

What does the update_task_by_name tool do? +

update_task_by_name. 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 update_task_by_name? +

Register the Todoist MCP Helper MCP server in PolicyLayer and add a rule for update_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 update_task_by_name? +

update_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 update_task_by_name? +

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

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

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