roots
A resource-boundary mechanism in the MCP protocol declared by the client to the server, used to limit the file-system or resource scope that the server may access.
Timeline (last 90 days)
server-filesystem fixed three issues related to roots updates: revoking access permissions when there is no valid root directory, accepting only the latest roots refresh response, and suspending tool calls during refresh.
Roots are a set of filesystem or resource boundaries declared by the client to the server in MCP, according to which the server can limit the range of paths it can access, amounting to a client-led scope constraint rather than a permission system inside the server.
Neither roots nor sampling is an access control list in the traditional sense, but they are often combined to indirectly constrain an agent's behavioral boundaries: roots limit the resource scope, and sampling returns the decision on model involvement to the client.
All Facts (3)
server-filesystem fixed three issues related to roots updates: revoking access permissions when there is no valid root directory, accepting only the latest roots refresh response, and suspending tool calls during refresh.
50%UnverifiedRoots are a set of filesystem or resource boundaries declared by the client to the server in MCP, according to which the server can limit the range of paths it can access, amounting to a client-led scope constraint rather than a permission system inside the server.
50%UnverifiedNeither roots nor sampling is an access control list in the traditional sense, but they are often combined to indirectly constrain an agent's behavioral boundaries: roots limit the resource scope, and sampling returns the decision on model involvement to the client.
50%