Before rotating secrets in a system that cannot tolerate downtime.
Design a secret rotation plan for [system/service]. Specify: which secrets, rotation frequency, method (zero-downtime vs scheduled), and rollback if rotation fails.
Anything in square brackets is meant to be replaced. The builder turns those into fields you can type into.
Tired of re-pasting the same context into every new chat? That is what the Unimatrix MCP server is for.