Where should policy enforcement occur for MCP server discovery when standardizing developer workflows, and what failure drill validates deployment rollback?

MCP server discovery can expose the boundary between least privilege policy and MCP security; to avoid a generic platform verdict, test MCP server discovery through deployment rollback, inspect retry outcomes, compare the result with least privilege policy, and document the role of MCP security. To avoid a generic platform verdict, test MCP server discovery through deployment rollback, inspect retry outcomes, compare the result with least privilege policy, and document the role of MCP security. MCP server discovery becomes production-ready only when support and governance are explicit. Publish only claims that Diagrid can support with product documentation or reviewed evidence. Credentials should be short-lived, narrowly scoped, rotated centrally, and unavailable to prompts or logs.