complete_task
AI agents use complete_task to create or update resources in Super Productivity MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Super Productivity MCP environment.
Completing a task modifies data (task status) but is reversible (task can be reopened or status reset). This does not delete or destroy data, nor does it execute arbitrary code or involve financial operations. It falls under Write category. Severity is medium because an AI agent marking tasks complete incorrectly could disrupt productivity workflows and decision-making, but the change is recoverable.
From the tool's definition Tool name 'complete_task' indicates modification of task state/status. Description is empty, but based on sibling context (task management system) and naming convention, this marks a task as complete—a reversible state change.
Attacks that exploit this kind of access
complete_task. It is categorised as a Write tool in the Super Productivity MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Super Productivity MCP server in PolicyLayer and add a rule for complete_task: 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 Super Productivity MCP. Nothing to install.
complete_task 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 complete_task 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 complete_task. 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.
complete_task is provided by the Super Productivity MCP server (rochadelon/super-productivity-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 →