Design a permissions model for connected tools in a multi-tenant product.

Instruction: Derive tenant identity from trusted authentication and enforce object access at every data operation.

Context: Prevent a multi-tenant assistant from reading or modifying another customer's records, even with a syntactically valid tool call.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would derive the principal and tenant from the authenticated request, then check operation permission and object-level access in the backend. A tool argument like tenant_id must never be the authority for switching tenants.

The host would expose only the capabilities relevant to the current workflow, but the server still...

Your preparation path

Work through these questions in order. Read the answer aloud, then explain it in your own words.

Related Questions