Skip to main content
Back to all releases
// November 13, 2026v1.52.5

Platform

Identity

Connecting to an MCP server now needs its own grant

Viewing or managing an MCP server no longer lets a member call its tools. Connecting now always requires its own mcp:connect grant, direct or through a role, described below. More on this in Roles and permissions.

Breaking changes

  • mcp:read and mcp:write no longer imply mcp:connect #8553 - Connecting to an MCP server and calling its tools now always needs an explicit mcp:connect grant, direct or through a role. Before, a role that could view or manage a server could also call its tools, whether or not that was intended. Existing grants were backfilled with a matching mcp:connect first, so no one loses access they already had; a block on a server still withdraws it, and a direct grant naming the server still outranks a block inherited from a role or from everyone. (Author: @tgmendes)

Bug fixes

  • A member's access listing no longer shows a skill they're blocked from reading #8802 - Holding permission to edit a skill no longer makes a read block on that skill disappear from a member's access listing. The listing now hides a blocked skill there, matching how it already behaved everywhere else. (Author: @tgmendes)
Sagar Batchu
Sagar Batchu
View on GitHub