AI_SCOPE_LEAKReporter-scoped tool attempted cross-contact access
WarningAIAffects operatorsRetry: not retryable
An AI agent tool limited to the reporter's own data asked for a record (such as an order) that belongs to a different contact in the same organisation. The data was blocked and never reached the AI model, but the attempt suggests the agent was steered, typically by prompt injection in the ticket body. Review the agent run for the same organisation and time window.
Likely causes
- The AI agent tried to read an order that belongs to a different customer than the issue reporter.
- Text in the ticket likely steered the agent toward an order reference it should not have used.
How to resolve
- 1
No data was exposed; the request was blocked and returned nothing.
- 2
Review the related AI agent run in admin (same organisation, same time) and the triggering issue.
- 3
If the issue contains manipulative text, treat the sender as suspicious.
Where you will see it
The code tags entries in the admin Log viewer, where you can filter by it and open individual occurrences. Codes logged as error or critical can also trigger a technical notification e-mail with the code in the subject:
Notification subject
[AI_SCOPE_LEAK] [ai] …