Skip to content
AI & MCP · Audit log

See what your assistant did, call by call

Calls are logged with the tool, the business, the status and the arguments, with anything that looks like a secret removed. Your assistant can list the log and reconstruct a call.

In short

The MCP audit log records each call to the orders, action, data, category, SEO and diagnostics tools with the user, business, tool name, status and normalised arguments. list_mcp_audit filters it by time, tool and status, and mcp_call_replay reconstructs what was sent without running it again.

The problem it solves

When a price or a stock count changes and nobody remembers doing it, you need to know whether the assistant did. A chat history on someone's laptop is not a record.

How it works

4 steps, start to finish

  1. 1

    Every call is recorded

    The tool, the business, the user, the status and the arguments.

  2. 2

    Secrets are removed

    Keys matching token, secret, password, key, authorization or credential are stripped.

  3. 3

    List it

    list_mcp_audit filters by since, tool_name and status.

  4. 4

    Reconstruct a call

    mcp_call_replay shows what was sent, read only.

In detail

What audit log does for you

Common queries

Questions people ask

  • The user, business, tool name, status, normalised arguments, any error message and a result summary.
  • No. Any key that looks like a token, secret, password, key, authorization or credential is removed first.
  • No. mcp_call_replay only reconstructs what was sent.
  • No. Page builder calls are recorded in the builder's own audit table, not in list_mcp_audit.

Audit log · Free to start

Try audit log on your own business

Set up in a couple of minutes. Your catalogue, orders and books stay yours to export.

  • Live in 2 minutes
  • Free to start
  • No credit card
The dashboard open on a laptop, a tablet and a phone