rename-shared-label · Todoist MCP: Risk & Policy

WHAT IT DOES

What rename-shared-label does on Todoist MCP

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

WHY IT NEEDS A POLICY

Why rename-shared-label needs a policy

Renaming a shared label modifies label attributes but does not delete data or cause irreversible damage. The change can be undone by renaming again. While it affects a shared resource (potentially impacting multiple users or tasks), the operation is reversible and does not rise to Destructive severity.

From the tool's definition Tool name 'rename-shared-label' and description 'Rename a shared label in Todoist' indicate modification of existing label metadata. This is a write operation that updates data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename-shared-label Rate-limited

rename-shared-label 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": {
    "rename-shared-label": {
      "limits": [
        {
          "counter": "rename-shared-label_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, so you can run agents against it safely.

FAQ

Questions about rename-shared-label

What does the rename-shared-label tool do? +

Rename a shared label in Todoist. It is categorised as a Write tool in the Todoist MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rename-shared-label? +

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

What risk level is rename-shared-label? +

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

Can I rate-limit rename-shared-label? +

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

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

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