rename_todoist_label
AI agents use rename_todoist_label 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.
Renaming a label modifies existing data (the label's name) but is fully reversible—the old name can be restored. This is a Write operation, not Read (it changes state) or Destructive (changes are undoable). Severity is medium because mislabeling tasks could cause organizational confusion and workflow disruption, but the impact is limited to a single workspace and easily corrected.
From the tool's definition Tool name 'rename_todoist_label' indicates modification of label metadata. Server description states it 'manage[s] projects and labels' and provides 'update' capabilities. Renaming is a reversible write operation.
Attacks that exploit this kind of access
rename_todoist_label. 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.
Register the Todoist MCP Server MCP server in PolicyLayer and add a rule for rename_todoist_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 Server. Nothing to install.
rename_todoist_label is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rename_todoist_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.
Set action: deny in the PolicyLayer policy for rename_todoist_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.
rename_todoist_label is provided by the Todoist MCP Server MCP server (stevesimpson418/todoist-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →