You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Third-party components (Python modules, external datasets — and for a harness, remote MCP servers) can be compromised. This PR renders a declaration audit for a resolved MCP plan: for every server, what is being introduced (transport, source, command/URL), what capabilities it declares (tool count + names), and what policy constrains it.
Output designed for
(a) Human review before first use of a server
(b) Regression diff when a config changes — a newly appearing server/tool in the diff is a supply-chain event worth noticing
(c) Feeding the allowlist decision for MCP server approval
API
ServerAuditEntry dataclass — one server's supply-chain declaration
audit_mcp_plan(plan) -> MCPAuditReport — full report with diff support
Pure mechanism — no network, no execution, no I/O
File
core/mcp/audit.py (new, 177 lines)
Part of GenAI lesson 13 supply-chain security family.
Thank you for the submission, @raymondginger2018-sudo. Closing because the module cannot run in this repository: it imports server_allowed from core.mcp.naming, which does not exist on main or on this branch (it refers to a PR that was not merged). The information it would render is already exposed by McpServerInfo in core/application/mcp_service.py (transport, command/url, approval mode, source, enabled tools, required env keys), and server resolution is already gated by project trust. If you want a risk summary for operators, a ~20-line addition to the mcp list view over McpServerInfo, with a test, is the shape we would merge.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Third-party components (Python modules, external datasets — and for a harness, remote MCP servers) can be compromised. This PR renders a declaration audit for a resolved MCP plan: for every server, what is being introduced (transport, source, command/URL), what capabilities it declares (tool count + names), and what policy constrains it.
Output designed for
(a) Human review before first use of a server
(b) Regression diff when a config changes — a newly appearing server/tool in the diff is a supply-chain event worth noticing
(c) Feeding the allowlist decision for MCP server approval
API
ServerAuditEntrydataclass — one server's supply-chain declarationaudit_mcp_plan(plan) -> MCPAuditReport— full report with diff supportFile
core/mcp/audit.py(new, 177 lines)Part of GenAI lesson 13 supply-chain security family.