Question 440
While investigating a FastMCP security review for fictional Elmcrest Theatre, the team reports: An MCP agent sends malformed VLAN filters and the tool silently falls back to querying every tenant's configuration. Which result most directly verifies that the proposed correction worked?
Explanation
Correct Answer
Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data. This directly verifies the related correction: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. It checks the technical distinction: Typed MCP tool schemas improve interoperability but server-side validation remains necessary even for a well-formed client call.
Incorrect Answers
The proposed action belongs to the mechanism: This directly verifies the related correction: Bind current request context to fresh authorized inventory and explicit tenant or device selection before tool calls. Here the stated fault follows a different mechanism: This directly verifies the related correction: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. The corrective choice is “Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data”.
The offered action targets: This directly verifies the related correction: Separate read-only diagnostic tools from mutating tools and require an explicit scoped approval step before any privileged operation. The case facts point instead to: This directly verifies the related correction: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. Implement “Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data” to address that specific condition.
This alternative is a response to another technical cause: This directly verifies the related correction: Ground actionable recommendations in trusted versioned technical references and reject unsupported or conflicting retrieved claims. The reported case instead depends on: This directly verifies the related correction: Define typed, validated tool arguments with explicit device allowlists and reject invalid or unauthorized inputs at the server boundary. The action that directly addresses it is “Malformed IDs and cross-tenant requests are rejected predictably while approved tool calls return scoped data”.