{"version":"2.1.310","anchor":"artifacts-mcp-filtering-also-applies-in-self-hosted-runner-c","canonical_anchor":"artifacts-mcp-filtering-also-applies-in-self-hosted-runner-c","heading":"Artifacts access is also cut off in self-hosted runner child sessions","tier":"notice","area":"Artifacts","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/artifacts-mcp-filtering-also-applies-in-self-hosted-runner-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Artifacts access is also cut off in self-hosted runner child sessions\n\nMCP servers that reach the Artifacts server are now left out of self-hosted runner child sessions where artifacts are disabled or the tool is denied\n\n**What**\n\nWhen artifacts are switched off, Claude Code already left out any MCP server entries that reach Claude Code Remote's Artifacts server. An MCP server is an add-on that gives Claude extra tools. The same filtering now also happens in a child session started by a self-hosted runner, when either:\n\n- that session's artifacts setting is disabled\n\n- the artifacts tool is denied\n\nThe log message about left-out entries has been reworded to say they were removed because they reach the Artifacts server.\n\n**Why**\n\nTurning artifacts off or denying the tool now holds in runner child sessions too, so they cannot reach artifacts through an MCP server.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}