Accept a project sharing invitation. Requires both the invitation ID and secret from the invitation email.
AI agents use todoist_invitation_accept to create or update resources in Mcp Todoist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Todoist environment.
Accepting an invitation modifies the user's project access and collaboration state—a Write operation. While it doesn't delete or execute code, it does create/establish a new relationship.
From the tool's definition Tool description states 'Accept a project sharing invitation', which creates or modifies a collaboration relationship by accepting an invitation. This is a reversible state change (the acceptance can be subsequently undone by removing collaborator access).
Attacks that exploit this kind of access
Accept a project sharing invitation. Requires both the invitation ID and secret from the invitation email. It is categorised as a Write tool in the Mcp Todoist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Todoist MCP server in PolicyLayer and add a rule for todoist_invitation_accept: 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_invitation_accept 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 todoist_invitation_accept 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_invitation_accept. 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_invitation_accept 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 →