renameSharedLabel · Todoist MCP Server MCP: Risk & Policy

WHAT IT DOES

What renameSharedLabel does on Todoist MCP Server

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

The tool renames a shared label, which is a reversible modification of data. While the description is empty (reducing confidence slightly), the name strongly indicates a Write operation that changes label metadata. This is less severe than Destructive (which would be deletion), and the blast radius of misusing a rename operation is contained to label naming — not critical functionality.

From the tool's definition Tool name is 'renameSharedLabel' which indicates it modifies an existing label through a rename operation. Sibling tools include 'createLabel' and 'deleteLabel', placing this clearly in the Write category as it updates data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

renameSharedLabel Rate-limited

renameSharedLabel 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": {
    "renameSharedLabel": {
      "limits": [
        {
          "counter": "renamesharedlabel_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 renameSharedLabel

What does the renameSharedLabel tool do? +

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

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

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

Can I rate-limit renameSharedLabel? +

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

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

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