Register for part 2 of our Device Identity Webinar Series!

Audit MCP Activity

The Smallstep MCP gateway records what AI agents do with the MCP servers behind it. This guide shows where to find those records in the Smallstep console and how to end a session.

The MCP gateway is in early access. Contact Smallstep to turn it on for your team.

Before you begin

You will need:

  • An MCP server behind the gateway. See Protect MCP Servers.
  • The Owner, Admin, or Device Admin role in Smallstep. Only an Owner or Admin can end a session.

What is recorded

The Audit page in the Smallstep console has three tabs:

TabWhat it showsRecorded when
SessionsOne row for each connection between an MCP client and an MCP server, with a timeline of its callsAlways
DecisionsThe outcome of each policy evaluationThe policy mode is Monitor or Enforce
EventsMCP activity next to your team's device and certificate eventsAlways

The gateway keeps sessions, timelines, and decisions for 30 days after a session ends.

Read sessions

In the Smallstep console, go to Audit → Sessions.

Each row is one session. A session belongs to the user and the device that opened it.

ColumnWhat it shows
StatusWhether the session is active, and how it ended
PrincipalThe user's email address, read from the device certificate
Device · clientThe device, and the name and version the MCP client reported, such as claude-code 2.1.327
ResourceThe MCP server's host
End reasonWhy the session ended, such as "closed by client" or "consent required"
EventsThe number of entries in the session's timeline

Search by user, device, or host, and filter by status.

The MCP client reports its own name and version. The gateway can't verify them.

The MCP gateway reference explains each status and end reason.

Read a session's timeline

Select a session to open its timeline. The timeline lists what happened in the session, in order:

decision · initialize                      allow   baseline-allow · Monitor · not enforced
token exchange                             token issued · → mcp.linear.app
session                                    active
initialize                                 HTTP 200 · 375 ms
decision · tools/call · search_documentation   allow   baseline-allow · Monitor · not enforced
tools/call · search_documentation          HTTP 200 · 1109 ms
session                                    ended · closed by client
EntryWhat it records
A method name, such as tools/call · save_issueOne call, with the MCP server's HTTP status and the time it took
decisionThe policy's outcome for the call that follows it, the policy that determined it, and the mode
token exchangeThe gateway got the user's access token for the MCP server
consentThe user has to approve access to the MCP server first
sessionA change in the session's status

Decision entries appear only when the policy mode is Monitor or Enforce.

A call that the gateway refused reads no upstream response, because the call never reached the MCP server. The decision before it reads deny and enforced.

While a session is active, the timeline updates as new calls arrive.

Record tool arguments

By default, the timeline shows a hash and the size of a tool call's arguments. It doesn't show the arguments.

To store the arguments:

  1. Go to Protect → MCP Gateway.
  2. Under Mode, turn on Capture tool arguments.

The timeline then shows the arguments of each tool call, up to 4 KiB for each call. Arguments larger than that aren't stored.

Tool arguments can hold sensitive data, such as the text of an issue or a search query. Turn capture on only if your team may store that data.

Read decisions

Go to Audit → Decisions.

The line at the top counts the decisions in the time range, by outcome. When some decisions in the range have the outcome would refuse, it also says how many calls Enforce would have refused.

OutcomeMeaning
allowThe policy allowed the call
would refuseThe policy denied the call, the mode was Monitor, and the call went ahead
denyThe policy denied the call, the mode was Enforce, and the call was refused

Each row shows the policy that determined the outcome, the MCP server and tool, the user, and the mode. A row that reads no matching policy means no permit statement matched the call.

Select a row to see more:

  • The user, the device, the session, the MCP client, the tool, and the method.
  • The policies that determined the outcome.
  • The activation that was in force, so you can read back the exact policy text.

A decision record holds IDs and hashes. It doesn't hold policy text or user attributes.

Read events

Go to Audit → Events and filter by the category MCP.

MCP events sit in the same list as your team's other events. You can read a device's enrollment, its certificates, and its MCP sessions in one place.

TypeWhen it's recorded
Session resolvedThe gateway matched a device certificate to a device and a user
Session startedThe MCP server accepted a new session
Session endedA session ended
Consent requiredA user has to approve access to an MCP server
Token issuedThe gateway got an access token for the MCP server
Tool calledA tool call passed the policy
Policy decisionThe gateway evaluated a call in Monitor or Enforce

End a session

  1. Go to Audit → Sessions.
  2. On an active session, choose Revoke.
  3. Choose Revoke session.

The gateway refuses the session's next request within 10 seconds. The agent's MCP proxy on the device stops with the message session not found, and the MCP client has to start it again.

Revoking ends one session. It doesn't block the user or the device, and the MCP client can open a new session. To keep someone out, use a forbid statement in Enforce, or remove the device from your inventory.

Next steps

Last updated on November 18, 2026

Audit AI Agent Activity Through the Smallstep MCP Gateway | Smallstep