Google Cloud remote Model Context Protocol (MCP) servers generate audit
logs to help you track administrative actions and access activities across
your resources. You can use these logs to monitor security compliance and audit
interactions with your MCP servers. For more information about Cloud Audit Logs,
see the following:

- [Types of audit logs](https://docs.cloud.google.com/logging/docs/audit.md.txt#types)
- [Audit log entry structure](https://docs.cloud.google.com/logging/docs/audit.md.txt#audit_log_entry_structure)
- [Storing and routing audit logs](https://docs.cloud.google.com/logging/docs/audit.md.txt#storing_and_routing_audit_logs)
- [Cloud Logging pricing summary](https://docs.cloud.google.com/stackdriver/pricing#logs-pricing-summary)
- [Enable Data Access audit logs](https://docs.cloud.google.com/logging/docs/audit/configure-data-access.md.txt)

## Service name

Audit logs for MCP servers are generated per service. To filter for MCP
audit logs:

    protoPayload.serviceName= "SERVICE_NAME/mcp"

Where <var translate="no">`SERVICE_NAME`</var> is the name of the service---for
example `bigquery.googleapis.com`. To get a list of enabled services, see
[List services](https://docs.cloud.google.com/service-usage/docs/list-services.md.txt).

## Permission types

Each Identity and Access Management permission has a `type` property, whose value is an enum that can be
one of four values: `ADMIN_READ`, `ADMIN_WRITE`, `DATA_READ`, or `DATA_WRITE`.
When you call a method, the service generates an audit log whose category
is dependent on the `type` property of the permission required to perform the
method.

Methods that require an Identity and Access Management permission with the `type` property value
of `DATA_READ`, `DATA_WRITE`, or `ADMIN_READ` generate
[Data Access](https://docs.cloud.google.com/logging/docs/audit.md.txt#data-access) audit logs.

Methods that require an Identity and Access Management permission with the `type` property value
of `ADMIN_WRITE` generate [Admin Activity](https://docs.cloud.google.com/logging/docs/audit.md.txt#admin-activity)
audit logs.

## Data access audit logs for MCP

Data Access audit logs for MCP are disabled by default because they can be
quite large. If you want Data Access audit logs to be written for Google Cloud
remote MCP server use, then you must explicitly enable them. Data Access audit
logs are written to the Google Cloud project whose data is accessed. Enabling
these logs might result in your Google Cloud project being charged for the
additional logs usage.

To enable Data Access audit logs for MCP only you must enable the `DATA_READ`
type for the service **Google Cloud MCP servers** . If you want to enable Data
Access audit logs for all services, enable `allServices`.

For more information about enabling and configuring Data Access audit logs, see
[Enable Data Access audit logs](https://docs.cloud.google.com/logging/docs/audit/configure-data-access.md.txt).

## System events

System Event audit logs are generated by Google Cloud systems, not direct user
action. For more information, see
[System Event audit logs](https://docs.cloud.google.com/logging/docs/audit.md.txt#system-event).