{"version":"2.1.312","anchor":"artifact-permission-check-no-longer-uses-the-allow-cobalt-pl","canonical_anchor":"artifact-permission-check-no-longer-uses-the-allow-cobalt-pl","heading":"Access check for the Artifacts MCP tools moved to a shared check","tier":"internal","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/artifact-permission-check-no-longer-uses-the-allow-cobalt-pl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Access check for the Artifacts MCP tools moved to a shared check\n\nThe check that decides whether the Artifacts MCP tools are available now runs through a shared check instead of its own\n\n**Unclear.** It is not clear whether this changes when the Artifacts MCP tools are available to you.\n\n**What**\n\nThe Artifacts MCP tools are tools for working with artifacts, which are pages Claude Code can publish. Before, their permission check had its own test of whether the Artifact tool was turned on in the session. If it was not, it refused with \"The Artifact tool isn't available in this session, so the Artifacts MCP tools aren't available either.\" That check now uses a shared one instead.\n\n**Why**\n\nThe rule that decides whether these tools can be used now lives in one shared place.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}