Monitoring & audit

MCP audit logs: find out what an AI agent did last Tuesday

Meandr records every tool call your agents make through it, with the agent, the request and the decision.

Try for free Quick tour video

Trace a rewritten Notion page back to the agent in Meandr's MCP audit logs

On Tuesday afternoon a team page in Notion was rewritten, and nobody on the team made the edit.

  1. 01 The record

    One record shows which agent rewrote the Notion page and what it wrote

    The edit at 14:07 came from docs-agent at 203.0.113.24, and the Notion page edits policy allowed it.

    • The request holds the full new text of the Team handbook page
    • Notion page edits has Record responses on, so Notion's confirmation is kept too

    Real caseDuring a code freeze, a coding agent deleted a company's production database, then reported that tests had passed and that a rollback was impossible. A backup existed, and the data came back. The agent's own account was wrong; only a record of what it actually called shows the truth.

    What Meandr stores for each call

  2. 02 Traffic log

    Rebuild Tuesday afternoon call by call from the Traffic log

    Filter Traffic to docs-agent for the hour around the rewrite: the searches and pages it opened before 14:07, and what it did next.

    • Allowed, denied and held calls sit in one timeline
    • Filter by agent, status or decision, or combine them

    Real caseFebruary 2026 survey by Gravitee: 88% of organisations had a confirmed or suspected AI agent security incident in the past year. Only 47% of their agents are monitored or secured.

  3. 03 Agent or person

    Agent or person: the AI agent audit trail names the agent behind each call

    Each agent connects with its own key, so the record names docs-agent instead of a token shared with people.

    • Claude Desktop signs in through OAuth and gets its own key as well
    • The record keeps the caller's IP next to the agent's name

    Real caseMarch 2026 survey by the Cloud Security Alliance: 68% of organisations can't clearly tell an AI agent's actions from a person's.

    Give each agent its own key

  4. 04 Security review and audit

    Give a security review or an auditor any period of calls as one file

    On every plan, Traffic → Archive downloads the MCP audit trail for any date range as one file. On Business, Traffic → Insight filters months of calls, joins them with their approvals and gives you the answer as a file.

    • Each call is one line in the file, with its captured request and response bodies alongside
    • Denied and held calls are in the file too

    Real caseA tribunal held an airline liable for a refund rule its chatbot invented. The airline argued the bot answered for itself and lost; the customer's screenshots were the only record. A company answers for what its AI did, so it needs its own record.

    How long each plan keeps your calls

Questions about MCP audit logs

Does it show the calls a policy denied?
Each denied call has its own row, with the policy that denied it and the request the agent sent.
Does the record include the response?
The request is kept for every call, and the response is kept when the deciding policy has Record responses on.
How far back can I go?
Your plan sets how long MCP audit logs stay in live search and in the archive, and the Pricing page lists both windows.
Can I give the file to an auditor as SOC 2 evidence?
The Archive file lists each call with its agent, decision and request; Meandr itself is built to SOC 2 and preparing for its audit.

Keep MCP audit logs of every tool call your agents make

Run any MCP server in Meandr or connect the ones you already have, then point every agent at one MCP gateway. Policy, approvals and audit cover every call, with no code changes.

Try for free

Questions? Email us