{"version":"2.1.260","anchor":"permission-denied-mcp-tool-errors-now-mark-the-mcp-client-as","canonical_anchor":"permission-denied-mcp-tool-errors-now-mark-the-mcp-client-as","heading":"Permission-denied MCP tool errors now mark the MCP client as needing auth via session wiring","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/permission-denied-mcp-tool-errors-now-mark-the-mcp-client-as","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Permission-denied MCP tool errors now mark the MCP client as needing auth via session wiring\n\nMCP auth-needed marking on permission errors was refactored, no behavior change expected.\n\nWhen a tool call throws an MCP permission-denied\/auth error, the code now marks the client as needing auth through `session.mcpSessionWiring.connections()?.markNeedsAuth(...)` instead of dynamically importing a helper module. This is an internal refactor of how MCP auth-needed state propagates, with no behavior change expected.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}