Move completed tasks older than a specified number of days from one list to another (archive) list. Useful for cleaning up active lists while preserving historical tasks.
AI agents use archive-completed-tasks to create or update resources in My MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your My MCP environment.
This tool modifies task metadata (list assignment/location) reversibly by moving tasks between lists. It does not permanently delete data—tasks are preserved in an archive list, making it a Write operation (reversible modification) rather than Destructive.
From the tool's definition Tool description states 'Move completed tasks older than a specified number of days from one list to another (archive) list', indicating modification of task state and organization through relocation rather than deletion.
Documented attack patterns abuse exactly the kind of access archive-completed-tasks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and My MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for archive-completed-tasks:
{
"version": "1",
"default": "deny",
"tools": {
"archive-completed-tasks": {
"limits": [
{
"counter": "archive-completed-tasks_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}archive-completed-tasks stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Move completed tasks older than a specified number of days from one list to another (archive) list. Useful for cleaning up active lists while preserving historical tasks. It is categorised as a Write tool in the My MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the My MCP server in PolicyLayer and add a rule for archive-completed-tasks: 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 My MCP. Nothing to install.
archive-completed-tasks 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 archive-completed-tasks 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 archive-completed-tasks. 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.
archive-completed-tasks is provided by the My MCP server (jordanburke/microsoft-todo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from My MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 My MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.