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.
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.
1. Start with the foundations
Build the vocabulary and explain the core decisions.
2. Apply it to a real workflow
Practice diagnosis, validation, and everyday tradeoffs.
3. Prepare for senior discussions
Explain failure boundaries, recovery, and production choices.
- Design a fallback strategy when tools are unavailable, degraded, or unauthorized. Member answer
- How do you implement MCP step-up authorization without losing scopes or retrying forever? Member answer
- An MCP request resumes after user confirmation. How would you validate its requestState? Member answer
Related Questions
-
easy
-
easy
-
easy
-
easy
-
easy
-
easy