completeTask
AI agents use completeTask to create or update resources in Todoist MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist MCP Server environment.
Completing a task is a reversible state change—tasks can typically be marked incomplete again. This is a modification operation (Write) rather than destructive. The severity is medium because mistaken completion of many tasks could create workflow disruption, but it's reversible.
From the tool's definition Tool name 'completeTask' indicates marking a task as complete/done in Todoist. While the description is empty, the naming convention and context within a task management system suggests this modifies task state (completion status) rather than creating new…
Attacks that exploit this kind of access
completeTask. It is categorised as a Write tool in the Todoist MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todoist MCP Server MCP server in PolicyLayer and add a rule for completeTask: 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.
completeTask 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 completeTask 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 completeTask. 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.
completeTask is provided by the Todoist MCP Server MCP server (stevengonsalvez/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 →