Safe multiplayer mode: Impersonation

[geoHeil]

The current basic wren MCP is great! It works well for a chatting with data experience - but only in single player mode.

I would love to see it extended and make it interoperate with:

• external context stores like https://datahub.com/
• secure ways of per-user interactions with a DB i.e. a databsae (snowflake, bigquery, postgres, ...) already should have a native user for the user sending the query against wren. The native user and its permissions (column level/row-level redactions) should be used when processing the data. this is called impersonation

[geoHeil]

Given https://www.getwren.ai/pricing describes parts of my wishes as part of the SaaS version of wren. Is this a contriubtion/topic wren OSS would even be interested in tackling?

[goldmedal]

Given https://www.getwren.ai/pricing describes parts of my wishes as part of the SaaS version of wren. Is this a contriubtion/topic wren OSS would even be interested in tackling?

Which part of the saas feature do you mean? The security one?

[geoHeil]

I do not know if the SaaS has this feature (but would commonly assume so) as security is usually part of an enterprise offering. I mean 2 points:

• full impersonation of the data access to the caller. Not a single shared service user
• optional the same thing on the metadata side as well - end user impersonation in scenarios where not every user can see even all the metadata

[goldmedal]

• full impersonation of the data access to the caller. Not a single shared service user

Makes sense to me 👍

Is this a contriubtion/topic wren OSS would even be interested in tackling?

Yes, we are happy to accept a PR for this feature. Some potential approaches:

• accept native impersonation syntax (e.g., Trino: SET SESSION AUTHORIZATION) so the session can impersonate any user dynamically.
• MCP server supports multiple users, and each user has their own connection (profile).

[geoHeil]

Let me think about this more. I fear that it may even warrant its whole own project given there would be pluggable data, pluggable metadata - not just wren style + secure impersonation + maybe data virtualization + pluggable IDP + multi-hop token-exchanges

at least this is the list of things which comes to my mind.