machines_archive
Archive (soft-delete) a machine. Cannot archive primary or machines with active tasks.
This record as markdown: /tools/todos/machines-archive.md
What machines_archive does on Todos
AI agents call machines_archive to permanently remove resources in Todos, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why machines_archive is rated Critical
Archiving is a soft-delete operation — it removes the machine from active use in a way that is not easily reversible through normal operations. While 'soft-delete' implies data is retained, the operational effect (machine no longer usable) is effectively irreversible without explicit restore action, placing it in the Destructive category.
From the tool's definition Archive (soft-delete) a machine. Cannot archive primary or machines with active tasks.
Attacks that exploit this kind of access
The rule that runs machines_archive safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For machines_archive, this is the rule to start with:
machines_archive is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every machines_archive call is checked against it from then on.
Questions about machines_archive
Archive (soft-delete) a machine. Cannot archive primary or machines with active tasks. It is categorised as a Destructive tool in the Todos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todos MCP server in PolicyLayer and add a rule for machines_archive: 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.
machines_archive is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the machines_archive 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 machines_archive. 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.
machines_archive 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.
More on Todos, and thousands of servers like it.
Across the catalogue