get_labels
AI agents call get_labels to retrieve information from Todoist MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_labels' follows the standard Read operation pattern (get/fetch/retrieve). It retrieves labels from Todoist with no apparent ability to modify or delete data. Sibling tools like 'add_label', 'delete_comment', and 'batch_update_labels' perform modifications, but this specific tool only retrieves existing label data. This is a low-severity operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'get_labels' which retrieves label data. The server description indicates this tool is part of the label management functionality that 'Supports batch operations and pagination', consistent with a query/retrieval operation.
Attacks that exploit this kind of access
get_labels. It is categorised as a Read tool in the Todoist MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Todoist MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_labels is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
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 →