# How should an agent handle an action that can affect an external system?

Canonical URL: https://help.iagenify.com/faqs/agent/how-should-an-agent-handle-an-action-that-can-affect-an-external-system

[← Back to Agent FAQs](https://help.iagenify.com/faqs/agent)

HELP CENTER · FAQ Agent 1 min read
# How should an agent handle an action that can affect an external system?
An action that sends a message, changes a remote record, or triggers a service can have effects beyond the workspace. The agent should identify the target and expected impact, verify the operation is within the user’s request, and use a preview or confirmation step when the action is consequential or hard to reverse.
IaGenify
Agent

## Inspect the action before execution
Confirm the destination, account, records, and exact change using available evidence. Do not infer a recipient or target from a similar name when the action could expose data or affect another person.
Check whether the user explicitly asked for this external action or only asked for a draft, analysis, or recommendation. A request to prepare content does not automatically authorize sending or publishing it.
## Verify and report the outcome
If the action is authorized and safe to perform, execute it once and inspect the resulting state or receipt. For operations that can time out, verify completion before retrying to avoid duplicates.
Report what changed and include the evidence available, such as a status or record identifier. If the tool cannot confirm whether the external effect occurred, state that uncertainty clearly. [← Back to Agent FAQs](https://help.iagenify.com/faqs/agent)