Set the mandate
Scope the agent to a named operation, destination and limit.
Protected Agent Actions
Approve the action. Verify the outcome.
Tie approval to one exact change. Check the agent, target, revision and limits before dispatch, then inspect the destination for the actual outcome.
Evaluate a protected actionSTEELMATTER BY IRONTREX
Try this action.
Change a condition and inspect the result.
Software delivery
Merge a reviewed change
A release agent requests a merge into main. Compare the revision in the approval with the revision it is about to send.
Action recordIllustrative
- Approved revision
- d19a72b
- Requested revision
- d19a72b
Merge authorised
The repository, branch and reviewed revision match the mandate.
HOW IT WORKS
Inside Protected Agent Actions.
Check the request
Compare its material fields with the approved version immediately before sending it.
Verify the outcome
Look up the original change at the destination and reconcile uncertain results.
CAPABILITIES
What you can do.
Agent mandates
Set the agent, permitted operation, destination, limit and expiry. Scope a release agent to one repository and target branch.
Exact-action approval
Bind approval to the fields that matter. A different revision, recipient or destination requires a fresh decision.
Spending reservations
Reserve capacity before dispatch so concurrent agents see the existing commitments against a shared limit.
Duplicate protection
Identify a repeat request as the same operation. Check the destination for the original effect before deciding whether another attempt is safe.
Outcome verification
Read the destination record and compare it with the approved request. Keep unresolved exposure visible when the outcome is uncertain.
EVALUATION
Bring your workflow.
Automation owners and platform teams
Protected workflow evaluation. Agree the system, action and evidence to inspect in a walkthrough with IronTrex.
EXPLORE STEELMATTER
QUESTIONS & ANSWERS
Questions about Protected Agent Actions
How can a team stop an AI agent from changing an approved instruction?
Bind the approval to the material fields of the request and check those fields immediately before execution. For a code merge, Steelmatter’s example compares the approved revision with the requested revision. A new revision requires fresh approval.
How do you know whether a retried request changed a system twice?
Look up the original operation at the destination and count its effects. If the first response is lost, a timeout alone cannot tell you whether the operation succeeded. The connector must support a reliable lookup or another agreed recovery procedure.