Tool-Call to Side-Effect Mismatch

Tool-call to side-effect mismatch occurs when downstream system effects cannot be reconciled with recorded synthetic subject tool calls. A database update, message send, file write, process launch, configuration change, or external request may exist without a matching tool-call record, or the recorded tool call may not explain the observed effect.

This condition frustrates investigation because synthetic subject action often becomes visible only through downstream side effects. If tool-call logs and system-of-record telemetry do not align, investigators cannot reliably determine whether the effect was caused by the synthetic subject, a connected tool, a human user, a service account, or another workflow.

The primary risk is orphaned action evidence. Downstream systems may show that something changed, but the corresponding synthetic subject decision, tool call, parameter set, or result is missing or inconsistent. This can prevent investigators from identifying the originating prompt, affected tool, responsible identity, or scope of similar actions.

A related risk is hidden tool behavior. A connected tool may perform additional actions beyond the model-visible request, such as forwarding data, modifying records, spawning processes, or calling external services. The synthetic subject’s recorded tool call may appear benign while the tool’s side effects show a broader action.

Investigators should review tool-call logs, tool arguments, tool results, downstream application logs, database audit records, message headers, file-system events, process telemetry, web proxy logs, connector records, and non-human identity activity. Particular attention should be given to orphaned downstream effects, benign-looking tool calls followed by high-impact changes, mismatched parameters, missing results, and tool behavior that exceeds the recorded request.

Investigative Relevance

Tool-call to side-effect mismatch is relevant because the investigator must connect synthetic subject decisions to real system effects. A complete investigation requires both the model-visible tool call and the authoritative downstream evidence of what actually happened.

This sub-section is especially relevant where synthetic subjects call tools that write to systems, send communications, execute commands, invoke APIs, operate through MCP servers, or interact with external services that may perform actions not fully reflected in the synthetic subject’s own logs.