Unattributed Tool Call

Unattributed tool call occurs when a synthetic subject invokes a tool without logs that clearly preserve the tool name, arguments, result, invoking synthetic subject, non-human identity, human invoker, and downstream action.

This configuration creates an elevated exposure condition because investigators may see only the final system change, not the tool call that caused it. The action may appear to originate from a service account, host application, or employee rather than a specific tool invocation.

The primary risk is loss of reconstructable evidence. Without immutable tool-call logging, investigators may be unable to determine what the synthetic subject requested, what the tool returned, what data was exposed, or whether the action matched an approved directive.

Investigators should review tool-call logs, application logs, agent traces, audit trails, non-human identity records, request identifiers, and downstream system events. Particular attention should be given to missing arguments, missing results, overwritten logs, shared service identities, and actions that cannot be tied to a specific tool call.

Investigative Relevance

Unattributed tool calls are relevant because tool use is often where synthetic subject behavior becomes operational action. This sub-section is especially relevant where agents call APIs, send messages, write records, execute commands, or interact with external services.