User Action Trigger

A user action trigger occurs when an action in an application interface starts an agent run. This may include submitting a form, clicking a button, saving a record, uploading a file, updating a field, or completing another workflow step.

This deployment pattern creates an elevated exposure condition because the action that starts the run may not be the same as the content that shapes it. The agent may process free-text fields, attachments, comments, descriptions, or uploaded records as task context, even where that content was supplied by an external or low-trust submitter.

The primary risk is delayed execution of injected content. A malicious instruction may be planted in a frontend field or submitted record, then executed later when an internal employee opens, reviews, routes, or processes the item. The run may execute under the application, workflow, or employee identity, while the effective instruction came from the external submitter.

Investigators should review the trigger action, submitted fields, attachments, record history, user identity, workflow permissions, agent run logs, tool calls, and downstream actions. Particular attention should be given to free-text fields, externally supplied content, and cases where an internal user triggered processing of a record created or modified by someone else.

Investigative Relevance

User action triggers are relevant because they allow external or low-trust content to influence an agent run through normal application behavior. The employee may appear to have initiated the run, but the instruction path may originate in submitted data.

This sub-section is especially relevant where agents process web forms, customer relationship management records, support tickets, uploaded files, comments, case notes, lead forms, application records, or other frontend-supplied content.