DEV-215183 - Add Collibra Data Access MCP tools

[wouterc-collibra]

🎯 What does this PR do?

Adds MCP tools for Collibra Data Access:

• search_data_access_identities - search Data Access users by name/email
• search_data_access_objects - search data objects (tables, columns, schemas, views, etc.)
• get_data_access_data_source - resolve a data source ID to name/type/description
• get_data_access_control_details - retrieve details of a single access control
• check_user_data_object_access - check whether a user has access to one or more data objects
• create_asset_access_request - create a Data Access request for a catalog asset

Also includes the collibra/data-access skill guiding agents through WHO/WHAT resolution before checking access or creating requests.

All six are behind the data-access experimental flag

The set is off by default and registers only under --experimental=data-access (or COLLIBRA_MCP_EXPERIMENTAL=data-access). create_asset_access_request writes to Data Access, so the whole set stays opt-in until it graduates rather than shipping the five read-only tools ahead of it.

Each tool also declares the scope it needs, so an instance without it fails with a named permission rather than an opaque error:

• all six require dgc.data-access-view-all-access-and-usage
• create_asset_access_request additionally requires dgc.data-access-create-access-controls

Unfiltered searches are rejected, not silently capped

search_data_access_objects and search_data_access_identities return status validation_error before any request is sent when the call would scan the whole instance — at least one real filter is required (name/dataSources/types/parents/ancestors, and name/email respectively). includeDeleted and pageSize do not count as filters. A pageSize outside 1–25 is rejected the same way instead of being silently clamped, so an agent can never believe it asked for 200 results and received them all.

About create_asset_access_request

Access is requested on a asset, and the WHAT of the request is the Data Access role linked to that asset. The tool resolves the role itself, so the caller never passes a role or a data object.

• Which assets can be requested is instance configuration, so the roles linked to an asset are read through ListAccessControls rather than inferred from its asset type. Resolution is the same for every asset type — there is no special handling for any particular one. An asset with no active Grant comes back as the no_role_linked status, with whatever is linked in linkedRoles, instead of an error.
• Beneficiaries are Collibra users and/or groups. Users map to Data Access users by email address, groups to Data Access groups by name — the only identifiers the two systems share. Nothing is created unless every beneficiary maps; failures come back in unresolvedUsers / unresolvedGroups.
• A purpose and an expiration date are mandatory. The purpose must come from the user and is used as the description, with a note appended stating the request was created by AI.
• name is optional. Pass it only when the user supplied one; otherwise omit it and Data Access generates a unique name itself. A name that is already taken comes back as status name_conflict with nothing created.
• A confirm checkpoint guards the write. confirm=false (the default) resolves the asset, the role and every beneficiary and returns status preview with the complete composed request — asset, role, mapped users and groups, description and expiration date — creating nothing. Only confirm=true creates it.

Requires data-access-go-sdk v0.0.73 for the assetIds access control filter.

Jira

DEV-215183

✅ Checklist

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation (if needed).
• My commit messages follow the Conventional Commits standard.

[svc-snyk-github-jira]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.