Hook Execution Logs

Review every Hook interception or modification, trace the inspection source for attachments and tool responses, control whether original message content is logged, and trace Hook execution details for

Every interception, modification, or pass performed by Hook is recorded. For regulated industries such as finance, healthcare, and government, traceability is itself a compliance requirement—when a problem occurs, you must be able to determine which message was processed by which rule, what action was taken, and when it happened.

The Audit Log records every action in full, including the matched rule, action taken, processing result, and timestamp. It supports keyword searches, filtering by assistant, and report exports.

1. View Execution Logs

From the left menu, go to AgentOps → Hook Execution Logs. For each execution, you can see:

• AI assistant—The AI assistant that triggered it

• Hook name and Hook type—The Hook that processed it

• Trigger point—When the Hook intervened (when receiving a user message / after an AI response was generated)

• Hook action and result—What it did (mask and modify / intercept and block / pass) and the processing result

• Message content and creation time—Which message was processed and when it occurred

You can filter by assistant, rule, type, action, action result, trigger point, date range, or keyword, and you can also export reports for further audit analysis. The top of the page also displays statistics for the total number of executions, number of matches, and match rate.

Execution log list: Each entry shows the AI assistant, Hook name, trigger point, action, and result. You can see actual actions such as Personal Data Masking replacing a phone number with [REDACTED_PHONE], or sensitive keywords and prompt injections being blocked.

View Details for an Individual Entry

Open any entry to view the full context of the action: basic information (Hook name, type, trigger point, action, and result), related information, message content, and Metadata. This lets you clearly understand what the system did.

Entry details: In this Personal Data Masking example, the action is modify and the message content has been masked as [REDACTED_PHONE].

Trace Checks on Attachments, Knowledge Bases, and Tool Responses

Hooks that run before content reaches the AI inspect more than user-entered text. Attachment content, passages retrieved from the knowledge base, and tool responses in Agent mode all pass through the same set of Hooks (see Four Sources). These checks also create execution log entries, with the trigger point shown as “When receiving a user message.” Open an entry and look in the Metadata section to see:

• path: input_context, indicating that this entry is for content that was not directly entered by the user

• source: Where the content came from—a tool response shows the tool name, while a passage from the knowledge base is shown as retrieved content

When you need to determine which tool or document supplied sensitive content to the model, use source to trace it back. Blocked content is not provided to the model, and the conversation itself does not stop.

2. Control Whether Original Messages Are Logged

By default, execution logs record only the processing result and do not retain the original sensitive content. This prevents personal data or sensitive messages from being stored again in the logs.

If you need to see the original content during debugging, go to the Hook settings page and change the Log original value before masking toggle from off to on. Once enabled, the logs also retain the original content before masking or blocking, making investigation easier.

Use the “Log original value before masking” field on the Hook settings page to control this behavior. The default is off (only the type and count are recorded; original personal data is not retained). Change it to on only when debugging is required.

Privacy trade-off: Enabling “Log original value” stores the original personal data or message content in the execution logs. For security reasons, we recommend keeping it disabled during normal operation and enabling it temporarily only when troubleshooting.

Execution logs for “Semantic Personal Data Masking” inherently contain no original text: the detection service returns only the location and type of personal data, so the logs retain only the types and counts that were masked.

3. View Hook Execution Details from a Conversation

In addition to the centralized execution logs, you can also trace actions from an actual conversation. Go to Customer Service Conversations → All Conversations and open any conversation. You can then see which messages in that conversation were processed by Hook (masked or blocked) and the corresponding action taken at the time.

This allows you to understand directly why a message was masked or blocked while reviewing a customer conversation, without having to cross-reference a separate log.

4. Related Pages

• Hook Message Interception Overview—What Hook is, the four sources, and the seven standard templates

• Add and Configure a Hook—How to create a Hook, configure parameters, and associate it with an AI assistant