Get all pending project sharing invitations received by the current user.
AI agents call todoist_invitations_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 queries and returns data about pending invitations without creating, modifying, deleting, or executing any operations. It is a simple data retrieval operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Get all pending project sharing invitations' — a retrieval operation with no modification or side effects. The verb 'Get' and absence of any write/delete/execute semantics confirm read-only behavior.
Attacks that exploit this kind of access
Get all pending project sharing invitations received by the current user. 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_invitations_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_invitations_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_invitations_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_invitations_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_invitations_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 →