Reopen a completed task.
AI agents use uncomplete_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.
This tool modifies task data reversibly by changing a task's completion status from done to not done. It is a Write operation because it updates data without destructive consequences—the original task data remains intact and the change is reversible (the task can be completed again). The blast radius is minimal as it only affects individual task state with no cascade effects or data loss.
From the tool's definition Tool name 'uncomplete_task' with description 'Reopen a completed task' indicates modification of existing task state from completed to incomplete.
Attacks that exploit this kind of access
Reopen a completed 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 uncomplete_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.
uncomplete_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 uncomplete_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 uncomplete_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.
uncomplete_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 →