How to retire an AI agent and take back its keys.

01Why agents outlive their purpose

Agents are cheap to start and nobody's job to stop. A pilot ends and its agent keeps its keys. A team reorganises and the agent's owner moves on. A better agent replaces it and the old one keeps running on a schedule, checking for work that never comes and paying for the check.

The scale is new. Palo Alto Networks' 2026 Identity Security Landscape, a survey of 2,930 security leaders, found machine identities, AI agents among them, now outnumber people 109 to 1, up from 82 to 1 a year earlier. Only 37 percent of organisations could revoke an AI agent's credentials.

Regulators have noticed. Singapore's Model AI Governance Framework for Agentic AI, updated in May 2026, names agent sprawl as a risk. It recommends that every agent identity and its permissions be issued from and tracked by a central system, so an organisation can see what it has deployed and remove identities it no longer needs. APRA's April 2026 letter to industry asks for ownership and accountability across the AI lifecycle, which ends with retirement.

02The triggers

• The purpose is done: the project ended, the pilot closed, the process changed.
• It was replaced by a newer agent doing the same work.
• Its owner left or moved, and nobody took it on within a set period.
• It has not run, or run usefully, for a set period.
• Its approval expired and nobody renewed it.
• It breached its scope or its cap, and the decision is to stop rather than fix.

Write the triggers into the approval. An agent approved with a review date and an owner has a natural end; an agent approved without them runs until someone notices.

03Seven steps to retire an agent

1. Confirm the owner and the decision. One person signs that the agent is to be retired, and when.
2. Stop the triggers. Disable its schedule, webhooks and any event that can start it.
3. Revoke its credentials. Every API key, token, service account and OAuth grant it holds, at the provider and in every system it reached.
4. Remove its access. Take it off the roles, groups and data shares it was given. Revoking the key without removing the role leaves a door for the next key.
5. Close its budget. Set its cap to zero and release its allocation, so any call that slips through is refused.
6. Hand over its work. Anything that still depends on it moves to its replacement or to a person, with a date.
7. Keep the record. Its row in the inventory is marked retired, with the date, the approver and what was revoked. The audit trail of what it did stays for as long as your retention rules require.

04Proving it is gone

A week after retirement, check three things: no model calls under its identity, no use of its credentials anywhere, and no budget drawn. Any of the three means something was missed. The check is quick when every call and every dollar is recorded against an agent, and slow when it means reading logs from every system the agent touched.