Restores a task from archive/ back to todos/ for further work. Use when a completed task needs to be reopened.
AI agents use unarchive_task to create or update resources in Project MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project MCP environment.
unarchive_task modifies task state by moving it from an archived location back to active todos, making it a Write operation (reversible state change). It does not delete, execute external code, or create financial obligations. Severity is medium because misuse could cause workflow confusion or unintended task resurrections, but the action is easily reversible by re-archiving.
From the tool's definition Tool description states it 'Restores a task from archive/ back to todos/' — this is a reversible modification of task state/location within the project management system.
Documented attack patterns abuse exactly the kind of access unarchive_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Project MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for unarchive_task:
{
"version": "1",
"default": "deny",
"tools": {
"unarchive_task": {
"limits": [
{
"counter": "unarchive_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}unarchive_task 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.
Restores a task from archive/ back to todos/ for further work. Use when a completed task needs to be reopened. It is categorised as a Write tool in the Project MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Project MCP server in PolicyLayer and add a rule for unarchive_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 Project MCP. Nothing to install.
unarchive_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 unarchive_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 unarchive_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.
unarchive_task is provided by the Project MCP server (pouyanafisi/project-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Project 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.
42 Project MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.