deixic
Log inRequest a demo

AI agent approval workflows

Hold a production change for a named approver.

Before an agent changes production, your Platform owner reviews the affected system, the plan, and how to roll it back. Deixic waits for their decision, then checks any approved change and records the result.

Request a demoReview the agent request
Example workflowAgent request

Production change

Apply a Terraform plan to production/networking

Identity
coding-agent · Platform
Target
production/networking
Cost
Recorded agent cost
Evidence
Plan diff and rollback steps

Policy decision

Production infrastructure changes require the Platform owner.

Approver
Platform owner
Awaiting approval

The tool call waits for its approval owner.

Approval applies to this request. The next request is checked again.

Put the decision before execution.

Execution order: the routed request reaches company policy before the connected tool runs.

  1. 01 · Request

    Inspect the change.

    The plan changes production routing and can interrupt customer traffic.

  2. 02 · Authority

    Name the approval owner.

    Production infrastructure changes require the Platform owner.

  3. 03 · Result

    Keep the tool result.

    Record the request, decision, and execution result in activity history.

Trace the action lifecycleApprove or deny a request

The next change starts with a reviewed procedure.

Save the steps and checks for reuse; the next action still needs its own identity, access, and authority.

Procedure
Production target, change plan, rollback and the owner's review steps.
Policy
Keep the company's approval boundary separate from the agent that requests the work.
Evidence and tests
Retain the decision and result; replay sessions to check changes to the procedure.

Execution requires a configured tool with provider permissions for this action. Review connector operations

Before you connect production work

Which actions does Deixic govern?

Deixic checks calls routed through its gateway against identity, connection access, and policy. Tools an agent uses directly remain under their existing controls.

Inspect the MCP gateway
Does one approval authorize the next change?

No. Approval belongs to the specific request. Keep the procedure and policy for reuse, and review the next request under its own authority.

Read the approval guide
Can we use a company-specific infrastructure tool?

Configure the connection with the provider permissions the action requires. Bring the tool, production target, and approval owner to the demo.

Review connector operations

Bring the first production change.

Request a demo