complete_task
AI agents use complete_task to create or update resources in RTM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RTM MCP Server environment.
Completing a task is a reversible state change (tasks can typically be marked incomplete again in task management systems). This is a Write operation rather than Destructive because it doesn't irreversibly delete data. Severity is medium because bulk misuse could mark many tasks as done, causing operational confusion, but the action is reversible.
From the tool's definition Tool name is 'complete_task' with no description provided. Based on the server context (Remember The Milk task management) and sibling tools including 'delete_task', 'add_task', 'edit_note', this tool modifies task state by marking tasks as complete/done.
Attacks that exploit this kind of access
complete_task. It is categorised as a Write tool in the RTM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RTM MCP Server 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 RTM MCP Server. 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 RTM MCP Server MCP server (ljadach/rtm-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 →