AI agents use unarchive_agent to create or update resources in Todos — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.
This tool modifies agent state from archived to active, which is reversible and represents data mutation. While the impact is relatively contained to agent lifecycle management, it could affect task assignments or workflows if misused by an AI agent (e.g., restoring unwanted agents). The medium severity reflects moderate blast radius in a task management context.
From the tool's definition The tool 'unarchive_agent' performs a state change operation: 'Restore an archived agent back to active status.' This is a modification that reverses a previous archival action, making it a Write operation rather than a Read (no retrieval-only) or Destructive…
Attacks that exploit this kind of access
Restore an archived agent back to active status. Resolve by id or name. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todos MCP server in PolicyLayer and add a rule for unarchive_agent: 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 Todos. Nothing to install.
unarchive_agent 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_agent 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_agent. 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_agent is provided by the Todos MCP server (@hasna/todos). 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 →