The agent identifies the correct modification flow, retrieves policy configuration details, and guides the user to add a human approval gate for specific actions like payments, ensuring compliance before execution.

For an existing integration, the user requests a policy change (e.g., requiring approval for payments). The agent queries the Alter Docs MCP server to find the specific modification flow for adding providers, secrets, agents, or runtime policies. It retrieves the necessary syntax for policy rules (such as require_approval) and guides the user to apply these changes via the CLI or SDK. The agent explains how the policy interacts with the Wallet's Limits tab and audit logs, ensuring the user understands the security implications before the CLI executes the change.

• Category: Software development
• Effect: Changes data in your accounts
• MCP servers: Alter Docs MCP (https://koskamo.com/explore/alter-docs-mcp)
• Source: Alter Docs MCP Server | Alter (https://docs.alterauth.com/mcp)
• Source quote: "Ask for the change in your own words: Require a human to approve every payment this agent makes through Stripe. The agent picks the matching modification flow — add a provider or secret, add an agent, rotate a key, manage a grant, or set a runtime policy ."
• Playbook page: https://koskamo.com/explore/use-cases/add-human-in-the-loop-approval-to-existing-integration

Prompt: Require a human to approve every payment this agent makes through Stripe.