Get information about the current Todoist user including name, email, timezone, karma, and account settings.
AI agents call todoist_user_get to retrieve information from Mcp Todoist without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user profile information (name, email, timezone, karma, account settings) without creating, modifying, or deleting any data. It is a straightforward read operation with no side effects. The severity is low because user profile information disclosure has limited blast radius compared to financial or destructive operations.
From the tool's definition Tool name 'todoist_user_get' and description states it 'Get[s] information about the current Todoist user' with no modification or deletion of data.
Attacks that exploit this kind of access
Get information about the current Todoist user including name, email, timezone, karma, and account settings. It is categorised as a Read tool in the Mcp Todoist MCP Server, which means it retrieves data without modifying state.
Register the Mcp Todoist MCP server in PolicyLayer and add a rule for todoist_user_get: 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 Mcp Todoist. Nothing to install.
todoist_user_get 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 todoist_user_get 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 todoist_user_get. 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.
todoist_user_get is provided by the Mcp Todoist MCP server (@greirson/mcp-todoist). 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 →