Payments service owner
The action waits until this owner approves or denies it.
Workflows · Credential rotation
The payments owner checks dependencies before credential rotation.
Record the credential reference, affected service, rotation evidence, policy decision, and provider result.
Agent request
Rotate the production payments API credential
A rotation without the dependent service update can stop payment requests from authenticating.
- Identity
- security-agent · Security engineering
- Target
- production/payments-api
- Cost
- Recorded agent cost
- Evidence
- Credential reference, dependent service, and validation check
Policy decision
Production credential rotations require the Payments service owner.
Tool call resumes
The secrets tool rotates the credential and records the provider result.
Tool call stays blocked
The current credential remains active and the rotation does not run.
Execution order
The agent request stops before the connected tool runs.
- 01Security agent requests the rotation
- 02Deixic checks the credential, dependency, evidence, and policy
- 03Payments service owner decides
- 04Connected secrets tool returns the rotation result
The request, decision, recorded cost, and execution result remain in activity history.