# audit operations

MCP tools and operation permissions for audit.

Generated from the shared operation catalog. Use [the JSON catalog](https://bytesmap.com/docs/reference/operations.json) for complete input schemas. Required dependency checks can be stricter than the resource permission listed below.

## audit_list

List workspace activity with actor, operation, resource, outcome and correlation ID. Requires audit read access. No credentials, SQL or result data are logged.

- **HTTP:** `GET /api/audit`
- **SDK:** `client.audit.list(input)`
- **Access:** workspace; audit / read
- **Effect annotation:** Read-only

| Input | Requirement | Description |
| --- | --- | --- |
| `eventType` | Optional | string |
| `actorUserId` | Optional | string |
| `resourceType` | Optional | string |
| `resourceId` | Optional | string |
| `source` | Optional | string |
| `outcome` | Optional | See schema |
| `from` | Optional | string |
| `to` | Optional | string |
| `cursor` | Optional | string |
| `limit` | Optional | integer |

## audit_settings_read

Read the current workspace audit status and retention policy. Requires audit read access; does not change logging or retention.

- **HTTP:** `GET /api/audit/settings`
- **SDK:** `client.audit.getSettings(input)`
- **Access:** workspace; audit / read
- **Effect annotation:** Read-only

See the JSON schema for this input contract.