DesignGen MCP Approval Policy
How connected agents should use DesignGen approval cards, workflow approvals, and autonomy policy.
Default policy
The safest default is approve_every_write. It lets agents inspect context freely while asking before write or spend actions.
- approve_every_write asks before write tools and paid generation work.
- budgeted_autonomy uses DesignGen approval rules plus workflow budgets.
- fully_autonomous is available only when the user explicitly chooses it during authorization or in Account Center.
Workflow approval cards
For carousel work, designgen_carousel (operation "start") can return a DesignGen workflow approval card.
- Present the card or fallback choices to the user.
- Keep approval actions disabled until the card has a live approvalId and designgen_approvals (operation "get") confirms the approval is still pending.
- Use designgen_approvals (operation "decide_card") after the user approves or changes quality, thinking budget, generation, or max credits.
- Generate-now approvals require a positive maxCredits budget that covers the estimated slide generations. Use plan-only when maxCredits is 0.
- If approval_not_found or a connection mismatch is returned, refresh the MCP connection if needed and regenerate the workflow approval.
- Do not ask the user to manually rerun designgen_carousel (operation "start") after a card decision.