What is the primary function of "roots" in the context of an MCP server?	Roots grant limited, codified access permissions to specific files and folders, restricting what the AI can interact with.
What major problem do roots solve regarding user file access?	They solve the issue of the AI being unable to search the entire, complex user file system and requiring users to provide full, absolute paths.
Name two new tools added to the MCP server to manage root access.	`read directory` and `list roots`.
What is the key benefit of using roots for the AI's workflow?	They allow the AI to autonomously search and locate files within defined, limited areas without needing a fully qualified path.
Who is responsible for enforcing the actual file and folder access limitations using roots?	The developer implementing the MCP server, not the SDK itself.
What must a developer implement to ensure a tool only accesses files within a root?	An access control function (e.g., `is path allowed`) that checks if the requested path is contained within one of the granted roots.
Besides calling a dedicated `list roots` tool, how else can the list of available roots be provided to the AI?	By manually including the list of roots directly in the prompt.