Question 40
At fictional Elmcrest Theatre, during a conversational network agent pilot, the operator observes: A multi-tenant MCP endpoint reuses a cached privileged token between separate customer sessions, exposing one site's inventory to another. Which targeted correction best addresses the network automation failure?
Explanation
Correct Answer
Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context. This addresses the problem because an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. Confirm success using: Two simulated tenants can query only their own device records and cross-tenant tool attempts are denied and audited.
Incorrect Answers
The proposed action belongs to the mechanism: aI-generated code may embed third-party patterns or dependencies; tool output is not automatically cleared of licensing obligations. Here the stated fault follows a different mechanism: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. The corrective choice is “Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context”.
The offered action targets: the model is not a reliable security principal; tool identities and server-side authorization bound the damage of agent errors. The case facts point instead to: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. Implement “Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context” to address that specific condition.
This alternative is a response to another technical cause: generative systems can propose plausible-looking but incorrect commands; independent executable validation is required for safe infrastructure changes. The reported case instead depends on: an MCP server is an integration boundary and must not treat model-selected identity strings as verified security credentials. The action that directly addresses it is “Authenticate each MCP client, authorize its tool calls by tenant identity and isolate credential/session context”.