Skip to main content
Use Authenticate before steps that require verified participant identity. A participant stating a name or account number is not verification.

​
Configure

  1. Select the MCP connection, Authentication challenge, and Trusted verifier.
  2. Bind the inputs required by the selected integration.
  3. Route both authenticated and denied, and handle error and timeout.
Use the trusted verification result to admit the participant to protected steps. Keep denied routes away from account-specific information and actions.

​
Outcomes

​
Scenario: protect an account lookup

A support workflow needs to read account-specific order details. Collect the integration’s required challenge information, then run Authenticate before the lookup Call MCP tool. Connect authenticated to the lookup. Connect denied to a general support message that does not reveal account data, then finish or provide an alternative support route. Authentication verifies identity; pair a later write action with Confirm action to obtain approval for that specific change.