> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.236/manage/mcp/mcp-audits.md).

# MCP Audits

### Overview

AI assistants can now create, update, and configure your integrations directly through MCP - which raises a natural question: what did the AI actually change, and when? **MCP Audits** answer that.

<code class="expression">space.vars.OIM</code> records an audit entry for every configuration change made in the application, capturing the entity that was changed, the user who changed it, when the change was made, the type of change, and the field-level values that changed. Every audit entry also records the **Origin** of the change - the channel it came through. Since the same user can make changes from the <code class="expression">space.vars.OIM</code> UI, the Admin API, or an MCP client, **Origin** makes it clear which one was used, so changes made by an AI assistant through MCP can always be told apart from the rest.

Audits are available for all audited entities, such as **Systems**, **Integrations**, **Mappings**, **Workflows**, **Users**, **Roles**, **Login Servers**, **Excel Uploads**, **Job Schedules**, **API Keys**, and **Processing Failures**. To view them, click the audit icon on the top right corner of the respective list view.

***

### Origin Values

| Value   | Description                                                                                  |
| ------- | -------------------------------------------------------------------------------------------- |
| **UI**  | The change was made from the <code class="expression">space.vars.OIM</code> user interface.  |
| **API** | The change was made through the [Admin API](/v7.236/manage/api/getting-started-with-api.md). |
| **MCP** | The change was made through an [MCP](/v7.236/manage/mcp/getting-started-with-mcp.md) client. |

***

### Filter and Sort by Origin

* The **Origin** filter is available on every audit screen. Select a value to view only the changes made through that channel - for example, select **MCP** to review everything an AI assistant changed. Click **Reset** to restore the default view.
* The **Origin** column can be sorted like the other columns, which is useful to group all the changes of a channel together.

***

### Important Notes

* **Historical audit records are displayed with Origin as UI** because the source channel was not captured before this <code class="expression">space.vars.OIM</code> version upgrade. To maintain a complete and consistent audit trail, existing audit entries are backfilled with the value **UI**. Changes made after the upgrade correctly capture and display their actual **Origin**, such as **UI**, **Admin API**, or **MCP**.
* Audit records show the account used to make the change, not the actual person behind it. If an MCP client or the Admin API uses a shared or service account, all changes will be recorded under that account. If you need to track changes back to a specific person, use individual user accounts or user-specific [API Keys](/v7.236/manage/administrator/api-key-management.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.opshub.com/v7.236/manage/mcp/mcp-audits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.