> ## Documentation Index
> Fetch the complete documentation index at: https://developer.box.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Give an AI agent secure, permission-aware access to enterprise documents
> Give an AI agent secure access to enterprise documents in Box. The Box MCP server and Box APIs act as the authenticated user or application. Scopes, collaborations, and waterfall permissions still apply.
export const RelatedLinks = ({title, items = []}) => {
const getBadgeClass = badge => {
if (!badge) return "badge-default";
const badgeType = badge.toLowerCase().replace(/\s+/g, "-");
return `badge-${badge === "ガイド" ? "guide" : badgeType}`;
};
if (!items || items.length === 0) {
return null;
}
return
;
};
export const Link = ({href, children, className, ...props}) => {
const localizedHref = localizeLink(href);
return
{children}
;
};
Connect the agent as an authenticated Box identity.
Use the hosted Box MCP server (`https://mcp.box.com`) when the agent supports MCP. Use the Box APIs, SDKs, or Box CLI when the agent runs code. Either way, the agent only sees files the authenticated user or application can already access.
Connecting any agent platform to Box does **not** bypass file permissions. Box checks collaborations, waterfall folder permissions, and application scopes on every request.
## How access works
Three layers apply on every request:
| Layer | What it controls |
| ----------------------- | ------------------------------------------------------------------------------------------------------------- |
| **Identity** | Who the agent is: an end user (OAuth) or a service account / CCG application. |
| **Scopes** | The maximum actions the integration can request. Scopes never grant access to files the identity cannot open. |
| **Content permissions** | Collaborations, waterfall folder permissions, shared links, Shield, and classification policies. |
The MCP server does not impersonate other users or search the enterprise unless the identity already can. See Does the Box MCP server bypass Box permissions?
## Choose an identity
The agent acts as the Box user who signs in. Use this for assistants that work on that person's files: Copilot, Cursor, Claude, Foundry Tools, and similar clients.
Enable MCP in the Admin Console, create integration credentials, and request only the scopes the agent needs. See Set up the MCP server.
Server-side jobs (extract on upload, publish to a hub, scheduled review) typically authenticate as a service account with Client Credentials Grant.
Collaborate that service account onto specific folders. Do not use a service account as a hidden superuser for an interactive agent. Downscope tokens when you pass credentials to a browser or untrusted runtime. See Downscope a token.
## Production versus local tests
Use a free developer account and sample files while you learn the tools. The Connect an AI agent to Box tutorial covers local setup and warns against pointing a coding agent at production content.
For production:
1. An admin enables MCP (or authorizes the Platform App) in the Admin Console.
2. Create dedicated integration credentials and request only the scopes you need.
3. Choose the Box user or service account deliberately. Collaborate it onto the folders the agent should access.
4. Test with that identity. If a file is missing from search or Ask, check collaborations first, not the model.
## Microsoft agent platforms
GitHub Copilot and Microsoft Foundry Tools connect to Box through MCP with the same permission model as any other client:
* The Box user who authorizes the connection is the identity.
* Admin-configured scopes cap what the client can request.
* SharePoint or Graph permissions do not replace Box permissions on Box files.
For setup steps, see Microsoft Foundry Tools and GitHub Copilot. For the tool list, see Available tools.
## Related patterns
* Query a curated knowledge base with hubs and Ask: Access-controlled AI knowledge base.
* Start with Box-managed retrieval before exporting to a vector index: Build RAG over enterprise documents stored in Box.