Action control guides
What lets an agent change production settings safely.
Deixic fixes failing controls by changing settings in your systems, from GitHub and AWS to Google Workspace, your HR system, and hundreds more. These guides cover the control behind each change: policy before execution, named approval, refusal, read-back, and a receipt.
MCP gateway versus action control
A gateway connects the tool. Action control decides whether this change runs.
How policy and named approval apply to one change in GitHub or AWS, and why a tool connection alone does not decide it.
Read guide →Identity and agent actionsIdentity names the caller. Policy decides whether its change runs.
Why an authenticated agent still needs policy, a named approver, and a receipt before it changes production identity and cloud settings.
Read guide →Production-agent control stackThe control stack puts a decision before every production change.
The chain from a failing control to an agent, a policy decision, a named approval, a change, a read-back, and a receipt.
Read guide →