batch_update_labels · Todoist MCP Server MCP: Risk & Policy

WHAT IT DOES

What batch_update_labels does on Todoist MCP Server

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

This tool modifies labels in bulk within Todoist—a reversible Write operation. It creates or changes label data without deletion or financial impact. Batch processing slightly increases blast radius (medium severity) compared to single operations, but labels are typically non-critical metadata. Confidence is 0.75 due to the empty description; inference relies on naming convention and context of sibling tools.

From the tool's definition Tool name 'batch_update_labels' combined with sibling tools 'add_label' and 'delete_label' on a task management server clearly indicates label modification. The 'batch_' prefix indicates multiple operations. Description is empty, reducing certainty slightly.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_update_labels Rate-limited

batch_update_labels 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": {
    "batch_update_labels": {
      "limits": [
        {
          "counter": "batch_update_labels_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 batch_update_labels

What does the batch_update_labels tool do? +

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

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

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

Can I rate-limit batch_update_labels? +

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

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

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