For a first Box MCP experiment, I would prefer to give an AI agent access to one test folder rather than all of my files. Can that boundary be enforced by the Box connection, or does it depend entirely on the permissions of the authorizing user?
Evgenii Arsentev covers the basic connection steps in his first MCP server guide. It is a general introduction, so I am looking for the Box-specific permissions to check before connecting real documents.
Hi
That’s a good precaution. With Box’s hosted MCP server, the agent acts as the Box user who authorizes the connection. Selecting a test folder in the agent’s instructions does not limit the connection to that folder.
Before connecting real documents, I’d check:
Which Box user will authorize OAuth: For a one-folder test, use a separate user with access only to the test folder. Check its owned files, folder and group collaborations, and shared-link access too.
The folder’s collaboration role: Give that user only the access needed for the experiment.
The integration’s scopes and enabled MCP tools: These control what actions the agent can request. Your Box admin can restrict available tools, including write actions, but those controls do not turn your regular user’s connection into a one-folder connection.
Box’s MCP access guide explains how identity, scopes, and content permissions work together. For a first test with sample files, Box also has a tutorial using an isolated developer account.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.