Get all collaborators from a project in Todoist
AI agents call get-project-collaborators to retrieve information from Todoist MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/queries a list of collaborators associated with a project. The verb 'Get' and the absence of any language indicating modification, deletion, or execution means this is a simple data retrieval operation. The blast radius of misuse is minimal—an LLM could retrieve information about who has access to a project, but cannot change permissions, delete users, or perform actions beyond reading.
From the tool's definition Tool name 'get-project-collaborators' and description 'Get all collaborators from a project' indicate a read-only retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get all collaborators from a project in Todoist. It is categorised as a Read tool in the Todoist MCP MCP Server, which means it retrieves data without modifying state.
Register the Todoist MCP server in PolicyLayer and add a rule for get-project-collaborators: 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. Nothing to install.
get-project-collaborators 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-project-collaborators 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-project-collaborators. 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-project-collaborators is provided by the Todoist MCP server (scofieldkoh/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 →