com.mcparmory/box
OCI · GHCR.IO/MCPARMORY/BOX:1.0.5 · 2 COMPONENTS · SCANNED SEP 20
Manage files, folders, and team collaboration with access controls
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 34690 tokens (~141/item across 246 items; 246 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety98
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 41 of 44 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "transfer_user_folders" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 246 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/box MCP server?
com.mcparmory/box runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/box:1.0.5. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/box:1.0.5
claude mcp add com-mcparmory-box -- docker run --rm -i ghcr.io/mcparmory/box:1.0.5
{
"mcpServers": {
"com-mcparmory-box": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/box:1.0.5"
]
}
}
} {
"servers": {
"com-mcparmory-box": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/box:1.0.5"
]
}
}
} codex mcp add com-mcparmory-box -- docker run --rm -i ghcr.io/mcparmory/box:1.0.5
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-box": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/box:1.0.5"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-box:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/box:1.0.5"] {
"McpServers": {
"com-mcparmory-box": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/box:1.0.5"
]
}
}
} {
"mcpServers": {
"com-mcparmory-box": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/box:1.0.5"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.83 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/box:1.0.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_file_versions List File Versions ~156
Retrieves the version history of a specific file, returning all past versions in paginated results. Version tracking is available only for Box premium accounts; use the get_file operation to retrieve the current version ID.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | The unique identifier of the file whose version history you want to retrieve. The file ID can be found in the URL when viewing the file in the Box web application. |
| limit | string | – | The maximum number of file versions to return per page. Accepts values up to 1000. |
| offset | string | – | The zero-based index of the item at which to start the response, used for paginating through results. Offset values exceeding 10000 will result in a 400 error. |
No output schema declared.
No examples provided.
list_file_versions_under_retention List File Versions Under Retention ~97
Retrieves a paginated list of file versions currently under retention for a specific retention policy assignment. Useful for auditing which file versions are being preserved by a given policy.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The maximum number of file version records to return per page. Accepts values up to 1000. |
| retention_policy_assignment_id | string | yes | The unique identifier of the retention policy assignment whose retained file versions you want to retrieve. |
No output schema declared.
No examples provided.
list_files_under_retention List Files Under Retention ~99
Retrieves a paginated list of files currently under retention for a specific retention policy assignment. Useful for auditing which files are actively governed by a given retention rule.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The maximum number of files to return per page. Accepts values up to 1000; omit to use the API default. |
| retention_policy_assignment_id | string | yes | The unique identifier of the retention policy assignment whose retained files you want to retrieve. |
No output schema declared.
No examples provided.
list_folder_app_item_associations List Folder App Item Associations ~159
Retrieves all app items associated with a folder, including associations inherited from ancestor folders. App item type and ID are visible to any user with folder access, regardless of View permission on the app item.
| Name | Type | Req | Description |
|---|---|---|---|
| application_type | string | – | Filters results to only include app items belonging to the specified application type. When omitted, associations for all application types are returned. |
| folder_id | string | yes | The unique identifier of the folder whose app item associations you want to retrieve. The folder ID appears in the URL when viewing the folder in the Box web app. The root folder is always ID 0. |
| limit | string | – | The maximum number of app item associations to return per page. Must be between 1 and 1000. |
No output schema declared.
No examples provided.
list_folder_collaborations List Folder Collaborations ~108
Retrieves all active and pending collaborations for a specified folder, returning details on users who currently have access or have been invited to collaborate.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | string | yes | The unique identifier of the folder whose collaborations you want to retrieve. Find this ID in the Box web app by opening the folder and copying the numeric ID from the URL. |
| limit | string | – | The maximum number of collaboration records to return in a single page of results. Accepts values up to 1000. |
No output schema declared.
No examples provided.
list_folder_items List Folder Items ~308
Retrieves a paginated list of files, folders, and web links contained within a specified folder. Use the dedicated Get Folder endpoint if you need metadata about the folder itself, such as its size.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | The sort direction for results, either ascending or descending alphabetical/numerical order. |
| folder_id | string | yes | The unique identifier of the folder whose contents you want to list. The root folder of any Box account always uses the ID '0'; for other folders, find the ID in the URL when viewing the folder in th… |
| limit | string | – | The maximum number of items to return in a single page of results. Accepted values range from 1 to 1000. |
| offset | string | – | The zero-based index of the first item to include in the response, used for offset-based pagination. Avoid high offset values on large datasets as reliability is not guaranteed; prefer marker-based p… |
| sort | string | – | The secondary attribute by which to sort items within their type grouping — items are always sorted by type first (folders, then files, then web links). Sorting by this field is not supported for mar… |
| usemarker | boolean | – | Set to true to enable marker-based pagination, which returns a 'marker' token in the response to fetch the next page. Cannot be combined with offset-based pagination; use one method consistently thro… |
No output schema declared.
No examples provided.
list_folder_locks List Folder Locks ~88
Retrieves all lock details for a specified folder, including lock type and restrictions. You must be authenticated as the owner or co-owner of the folder to use this endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | string | yes | The unique identifier of the folder whose locks you want to retrieve. You can find this ID in the folder's URL in the Box web application; the root folder is always ID `0`. |
No output schema declared.
No examples provided.
list_folder_metadata List Folder Metadata ~111
Retrieves all metadata instances attached to a given folder. Cannot be used on the root folder (ID `0`).
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | string | yes | The unique identifier of the folder whose metadata instances will be retrieved. Find this ID in the Box web app URL when viewing the folder. |
| view | string | – | Controls how taxonomy field values are represented in the response. By default, taxonomy values are returned as node identifiers (API view); set to `hydrated` to return full taxonomy node details ins… |
No output schema declared.
No examples provided.
list_global_metadata_templates List Global Metadata Templates ~74
Retrieves all generic, global metadata templates available to every enterprise using Box. These templates are not organization-specific and can be applied universally across all Box accounts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The maximum number of metadata templates to return per page. Accepts values up to 1000; omit to use the default page size. |
No output schema declared.
No examples provided.
list_group_collaborations List Group Collaborations ~128
Retrieves all collaborations for a specified group, showing which files or folders the group can access and with what role. Requires admin permissions to inspect enterprise groups.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The unique identifier of the group whose collaborations you want to retrieve. |
| limit | string | – | The maximum number of collaboration records to return per page. Accepts values up to 1000. |
| offset | string | – | The zero-based index of the first item to include in the response, used for paginating through results. Offset values exceeding 10000 will result in a 400 error. |
No output schema declared.
No examples provided.
list_group_members List Group Members ~91
Retrieves all membership records for a specified group, including details about each member. Accessible only to members of the group or users with admin-level permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The unique identifier of the group whose members you want to retrieve. |
| limit | string | – | The maximum number of membership records to return per page. Accepts values up to 1000; omit to use the API default. |
No output schema declared.
No examples provided.
list_groups List Groups ~135
Retrieves all groups belonging to the enterprise, with optional filtering by name. Requires admin permissions to access enterprise group data.
| Name | Type | Req | Description |
|---|---|---|---|
| filter_term | string | – | Narrows results to only groups whose name begins with the specified search term. Omitting this parameter returns all groups. |
| limit | string | – | Maximum number of groups to return in a single page of results. Accepts values between 1 and 1000. |
| offset | string | – | Zero-based index of the first item to include in the response, used for paginating through results. Offsets greater than 10000 are not permitted and will return a 400 error. |
No output schema declared.
No examples provided.
list_legal_hold_assignment_file_versions List Legal Hold Assignment File Versions ~115
Retrieves a paginated list of previous (past) file versions placed on hold for a specific legal hold policy assignment. Use this endpoint for historical file versions; for current file versions on hold, use the files_on_hold endpoint instead.
| Name | Type | Req | Description |
|---|---|---|---|
| legal_hold_policy_assignment_id | string | yes | The unique identifier of the legal hold policy assignment whose past file versions on hold should be retrieved. |
| limit | string | – | The maximum number of file version records to return per page. Accepts values up to 1000. |
No output schema declared.
No examples provided.
list_legal_hold_assignment_files List Legal Hold Assignment Files ~101
Retrieves a paginated list of files with their current file versions held under a specific legal hold policy assignment. For previous file versions on hold, use the file versions on hold endpoint instead.
| Name | Type | Req | Description |
|---|---|---|---|
| legal_hold_policy_assignment_id | string | yes | The unique identifier of the legal hold policy assignment whose held files you want to retrieve. |
| limit | string | – | The maximum number of files to return per page, up to a maximum of 1000. |
No output schema declared.
No examples provided.
list_legal_hold_policies List Legal Hold Policies ~91
Retrieves all legal hold policies belonging to the enterprise. Supports filtering by policy name prefix to narrow results.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The maximum number of legal hold policies to return in a single page of results. Accepts values up to 1000. |
| policy_name | string | – | Filters results to only include policies whose names begin with this search term. The match is case-insensitive. |
No output schema declared.
No examples provided.
list_legal_hold_policy_assignments List Legal Hold Policy Assignments ~182
Retrieves a list of all items (files, folders, users, etc.) that a specific legal hold policy has been assigned to. Supports filtering by item type and item ID for targeted lookups.
| Name | Type | Req | Description |
|---|---|---|---|
| assign_to_id | string | – | Narrows results to only assignments targeting a specific item by its unique ID. Best used in combination with assign_to_type for precise filtering. |
| assign_to_type | string | – | Narrows results to only assignments targeting a specific item type. Accepted values are 'file', 'file_version', 'folder', 'user', 'ownership', or 'interactions'. |
| limit | string | – | The maximum number of assignments to return in a single page of results. Accepts values up to 1000. |
| policy_id | string | yes | The unique identifier of the legal hold policy whose assignments you want to retrieve. |
No output schema declared.
No examples provided.
list_metadata_cascade_policies List Metadata Cascade Policies ~167
Retrieves all metadata cascade policies applied to a specific folder, which automatically apply metadata templates to items within that folder. Cannot be used on the root folder (ID `0`).
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | string | yes | The ID of the folder for which to retrieve metadata cascade policies. Must be a valid non-root folder; the root folder with ID `0` is not supported. |
| offset | string | – | The zero-based index of the first item to include in the response, used for paginating through results. Must not exceed 10000; requests with a higher offset will be rejected with a 400 error. |
| owner_enterprise_id | string | – | The ID of the enterprise whose metadata cascade policies should be returned. Defaults to the currently authenticated enterprise if not provided. |
No output schema declared.
No examples provided.
list_metadata_taxonomies List Metadata Taxonomies ~89
Retrieves all metadata taxonomies within a specified namespace, enabling discovery of available taxonomy structures for organizing and classifying content metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The maximum number of taxonomy items to return in a single page of results, up to a maximum of 1000. |
| namespace | string | yes | The namespace that scopes the metadata taxonomies to retrieve, typically representing an enterprise or organizational boundary. |
No output schema declared.
No examples provided.
list_pending_collaborations List Pending Collaborations ~128
Retrieves all pending collaboration invites for the authenticated user. Returns a paginated list of collaborations awaiting the user's response.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Limits the number of collaboration records returned in a single page. Accepts values up to 1,000. |
| offset | string | – | Zero-based index of the first item to include in the response, used for paginating through results. Must not exceed 10,000; requests beyond this limit will return a 400 error. |
| status | string | yes | Filters collaborations by their current status. Only pending invites are supported by this endpoint. |
No output schema declared.
No examples provided.
list_recent_items List Recent Items ~71
Retrieves a list of items recently accessed by the current user, covering activity from the last 90 days or up to the last 1000 items accessed, whichever limit is reached first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The maximum number of recently accessed items to return. Accepts values up to 1000. |
No output schema declared.
No examples provided.
list_retention_policies List Retention Policies ~205
Retrieves all retention policies configured for the enterprise, with optional filtering by name, type, or creator. Useful for auditing data governance rules or locating specific policies before applying or modifying them.
| Name | Type | Req | Description |
|---|---|---|---|
| created_by_user_id | string | – | Filters results to only policies created by the user with the specified user ID. Useful for auditing or managing policies owned by a particular administrator. |
| limit | string | – | Limits the number of retention policies returned per page. Accepts values up to 1000; omitting this parameter returns the default page size. |
| policy_name | string | – | Filters results to only retention policies whose names begin with the specified string. The match is case-sensitive and prefix-based, so partial names from the start of the policy name are supported. |
| policy_type | string | – | Filters results by the retention policy type. Use 'finite' for policies with a defined expiration period, or 'indefinite' for policies that retain content without a set end date. |
No output schema declared.
No examples provided.
list_retention_policy_assignments List Retention Policy Assignments ~131
Retrieves all assignments for a specified retention policy, showing which folders, enterprise, or metadata templates the policy is applied to. Optionally filter results by assignment type and control page size.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The maximum number of assignments to return in a single page of results. Accepts values up to 1000. |
| retention_policy_id | string | yes | The unique identifier of the retention policy whose assignments you want to retrieve. |
| type | string | – | Filters the results to only return assignments of a specific type. Accepted values are 'folder', 'enterprise', or 'metadata_template'. |
No output schema declared.
No examples provided.
list_shield_information_barriers List Shield Information Barriers ~72
Retrieves all shield information barriers configured for the enterprise associated with the JWT token. Shield information barriers restrict communication and data access between internal groups.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The maximum number of shield information barrier records to return in a single page of results. Must be between 1 and 1000. |
No output schema declared.
No examples provided.
list_sign_requests List Sign Requests ~170
Retrieves all Box Sign signature requests created by the authenticated user. Requests associated with deleted sign files or parent folders are excluded from results.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Maximum number of signature requests to return per page. Accepts values up to 1000. |
| senders | array | – | Filters results to only include signature requests sent by the specified email addresses. Requires `shared_requests` to be set to `true` when used. Order is not significant; each item should be a val… |
| shared_requests | boolean | – | When `true`, returns only signature requests where the authenticated user is a collaborator (not the owner); collaborator access is determined by the user's access level on the associated sign files.… |
No output schema declared.
No examples provided.
list_sign_templates List Sign Templates ~60
Retrieves all Box Sign templates created by the authenticated user. Returns a paginated list of templates available for use in signing workflows.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The maximum number of sign templates to return per page. Accepts values up to 1000. |
No output schema declared.
No examples provided.
list_slack_integration_mappings List Slack Integration Mappings ~204
Retrieves all Slack integration mappings for the enterprise, showing how Box folders are linked to Slack channels. Requires Admin or Co-Admin role.
| Name | Type | Req | Description |
|---|---|---|---|
| box_item_id | string | – | Filters results to only return mappings associated with the specified Box item ID. |
| box_item_type | string | – | Filters results to only return mappings for the specified Box item type. Currently only 'folder' is supported. |
| is_manually_created | boolean | – | Filters results to only return mappings that were manually created (true) or automatically created (false). |
| limit | string | – | Maximum number of integration mappings to return per page. Accepts values up to 1000. |
| partner_item_id | string | – | Filters results to only return mappings associated with the specified Slack partner item ID, such as a specific Slack channel ID. |
| partner_item_type | string | – | Filters results to only return mappings for the specified Slack item type. Currently only 'channel' is supported. |
No output schema declared.
No examples provided.
list_storage_policy_assignments List Storage Policy Assignments ~98
Retrieves all storage policy assignments for a specified enterprise or user. Returns the storage policies currently assigned to the given target.
| Name | Type | Req | Description |
|---|---|---|---|
| resolved_for_id | string | yes | The unique identifier of the user or enterprise whose storage policy assignments should be retrieved. Must correspond to the entity type specified in resolved_for_type. |
| resolved_for_type | string | yes | The type of entity to retrieve storage policy assignments for, either a specific user or an entire enterprise. |
No output schema declared.
No examples provided.
list_task_assignments List Task Assignments ~50
Retrieves all assignments associated with a specific task, returning the list of users or groups assigned to it.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The unique identifier of the task whose assignments you want to retrieve. |
No output schema declared.
No examples provided.
list_taxonomy_field_options List Taxonomy Field Options ~377
Retrieves available taxonomy nodes for a specific taxonomy field within a metadata template, filtered by level, parent, ancestor, or search query. Results are sorted lexicographically by default, or by relevance when a query is provided.
| Name | Type | Req | Description |
|---|---|---|---|
| ancestor | array | – | Filters results to nodes that are descendants of the specified ancestor node identifiers at any depth. Multiple values may be provided; nodes matching any specified ancestor are included. |
| field_key | string | yes | The key identifying the specific taxonomy field within the metadata template whose options are being retrieved. |
| include-total-result-count | boolean | – | When set to true, the response includes the total count of nodes matching the query, computed for up to 10,000 results. Defaults to false. |
| level | array | – | Filters results to taxonomy nodes at the specified depth levels. Multiple values may be provided; nodes matching any specified level are included. |
| limit | string | – | The maximum number of taxonomy nodes to return in a single page of results. Must be between 1 and 1000. |
| namespace | string | yes | The namespace that scopes the metadata taxonomy, typically tied to an enterprise account. |
| only-selectable-options | boolean | – | When set to true, restricts results to only those taxonomy nodes that are valid selectable options for this field. When false, all taxonomy nodes are returned regardless of selectability. Defaults to… |
| parent | array | – | Filters results to nodes that are direct children of the specified parent node identifiers. Multiple values may be provided; nodes matching any specified parent are included. |
| query | string | – | Free-text search string to find matching taxonomy nodes by name or label. When provided, results are ranked by relevance rather than lexicographic order. |
| template_key | string | yes | The unique key identifying the metadata template that contains the taxonomy field. |
No output schema declared.
No examples provided.
list_taxonomy_nodes List Taxonomy Nodes ~314
Retrieves nodes within a specific metadata taxonomy, supporting filtering by level, parent, or ancestor relationships. Results are sorted lexicographically by default, or by relevance when a search query is provided.
| Name | Type | Req | Description |
|---|---|---|---|
| ancestor | array | – | Filters nodes to only those that are descendants of the specified ancestor node identifier(s) at any depth. Multiple values may be provided; nodes matching any specified ancestor are returned. |
| include-total-result-count | boolean | – | When set to true, includes the total count of matching nodes in the response. Counts are computed for up to 10,000 matching elements; defaults to false. |
| level | array | – | Filters nodes to only those at the specified depth level(s) within the taxonomy hierarchy. Multiple values may be provided; nodes matching any specified level are returned. |
| limit | string | – | The maximum number of taxonomy nodes to return in a single page of results. Must be between 1 and 1,000. |
| namespace | string | yes | The namespace that owns the metadata taxonomy, used to scope the taxonomy to a specific organization or enterprise. |
| parent | array | – | Filters nodes to only those whose immediate parent matches the specified node identifier(s). Multiple values may be provided; nodes matching any specified parent are returned. |
| query | string | – | Free-text search string to find matching taxonomy nodes by name or content. When provided, results are ranked by relevance rather than lexicographic order. |
| taxonomy_key | string | yes | The unique key identifying the metadata taxonomy within the given namespace. |
No output schema declared.
No examples provided.
list_teams_integration_mappings List Teams Integration Mappings ~149
Retrieves a list of Box for Teams integration mappings within an enterprise, showing how Box items are linked to Microsoft Teams channels or teams. Requires Admin or Co-Admin role.
| Name | Type | Req | Description |
|---|---|---|---|
| box_item_id | string | – | Filters results to only return mappings associated with the specified Box item ID. |
| box_item_type | string | – | Filters results to only return mappings for the specified Box item type. Currently only folder mappings are supported. |
| partner_item_id | string | – | Filters results to only return mappings associated with the specified Microsoft Teams item ID. |
| partner_item_type | string | – | Filters results to only return mappings for the specified Microsoft Teams item type, either a channel or a team. |
No output schema declared.
No examples provided.
list_terms_of_service_user_statuses List Terms of Service User Statuses ~99
Retrieves the acceptance status of users for a specific terms of service, including whether each user has accepted the terms and the timestamp of their response. Optionally filter results to a single user.
| Name | Type | Req | Description |
|---|---|---|---|
| tos_id | string | yes | The unique identifier of the terms of service whose user acceptance statuses should be retrieved. |
| user_id | string | – | When provided, restricts the results to the acceptance status of a single user matching this ID. |
No output schema declared.
No examples provided.
list_trash_items List Trash Items ~187
Retrieves all files and folders currently in the trash. Supports offset-based and marker-based pagination, and allows sorting and filtering by specific attributes using the fields parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | The sort direction for results, either ascending or descending alphabetical order. Items are always grouped by type first (folders, then files, then web links) before this ordering is applied. |
| limit | string | – | The maximum number of items to return per page. Must be between 1 and 1000. |
| offset | string | – | The zero-based index of the first item to include in the response, used for offset-based pagination. Offsets exceeding 10000 will result in a 400 error. |
| sort | string | – | The secondary attribute by which to sort items within each type group. Items are always sorted by type first; this parameter is not supported when using marker-based pagination. |
No output schema declared.
No examples provided.
list_upload_session_parts List Upload Session Parts ~131
Retrieves a paginated list of all file chunks uploaded so far within a specific upload session, allowing you to track multipart upload progress.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The maximum number of uploaded parts to return in a single response. Accepts values up to 1000. |
| offset | string | – | The zero-based index of the first item to return, enabling pagination through large result sets. Must not exceed 10000; requests beyond this limit will be rejected with a 400 error. |
| upload_session_id | string | yes | The unique identifier of the upload session whose uploaded parts you want to list. |
No output schema declared.
No examples provided.
list_user_email_aliases List User Email Aliases ~58
Retrieves all secondary email aliases associated with a specific user account. Note that the user's primary login email is not included in the returned collection.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | The unique identifier of the user whose email aliases should be retrieved. |
No output schema declared.
No examples provided.
list_user_memberships List User Memberships ~80
Retrieves all group memberships for a specified user. Accessible only to members of the same group or users with admin-level permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The maximum number of group memberships to return per page. Accepts values up to 1000. |
| user_id | string | yes | The unique identifier of the user whose group memberships are being retrieved. |
No output schema declared.
No examples provided.
list_users List Users ~250
Retrieves a paginated list of all enterprise users, including their user ID, public name, and login. Requires the authenticated user and application to have enterprise-wide user lookup permissions.
| Name | Type | Req | Description |
|---|---|---|---|
| external_app_user_id | string | – | Restricts results to app users that were created with the specified external_app_user_id value, allowing lookup of app users by your own identifier assigned at creation time. |
| filter_term | string | – | Narrows results to users whose name or login starts with the given term. For externally managed users, the term must be an exact match and will return at most one result. |
| limit | string | – | Maximum number of users to return in a single response page. Accepts values up to 1000. |
| offset | string | – | Zero-based index of the first item to include in the response, used for paginating through large result sets. Must not exceed 10000. |
| user_type | string | – | Filters results by user category: 'all' includes every user type with partial name/login matching (exact match required for external users), 'managed' returns only managed and app users with partial… |
No output schema declared.
No examples provided.
list_webhooks List Webhooks ~85
Retrieves all webhooks defined for the authenticated application, scoped to files and folders owned by the requesting user. Note that admins cannot view webhooks created by service accounts unless they have explicit access to those folders, and vice versa.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | The maximum number of webhooks to return in a single page of results. Must be between 1 and 1000. |
No output schema declared.
No examples provided.
list_workflows List Workflows ~153
Retrieves all workflows associated with a specific folder that have a manually triggerable flow. Requires the Manage Box Relay application scope to be enabled in the developer console.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | string | yes | The unique identifier of the folder whose associated workflows you want to retrieve. The root folder of a Box account is always ID 0; other folder IDs can be found in the URL when viewing the folder… |
| limit | string | – | The maximum number of workflows to return in a single response, up to a limit of 1000. |
| trigger_type | string | – | Filters workflows by their trigger type, returning only workflows that match the specified trigger. Use to narrow results to a specific trigger category. |
No output schema declared.
No examples provided.
lock_folder Lock Folder ~105
Creates a lock on a folder to prevent it from being moved and/or deleted. You must be the owner or co-owner of the folder to perform this action.
| Name | Type | Req | Description |
|---|---|---|---|
| delete | boolean | – | Whether to lock the folder against deletion, preventing it from being permanently removed. |
| id | string | – | The unique identifier of the folder on which to apply the lock. |
| move | boolean | – | Whether to lock the folder against move operations, preventing it from being relocated within the file system. |
No output schema declared.
No examples provided.
permanently_delete_trashed_file Permanently Delete Trashed File ~80
Permanently deletes a file that is currently in the trash, freeing storage and removing it from Box entirely. This action is irreversible and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | The unique identifier of the trashed file to permanently delete. The file ID can be found in the URL when viewing the file in the Box web application. |
No output schema declared.
No examples provided.
permanently_delete_trashed_folder Permanently Delete Trashed Folder ~80
Permanently deletes a folder that is currently in the trash, freeing storage and removing it from Box entirely. This action is irreversible and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | string | yes | The unique identifier of the folder to permanently delete from trash. The folder ID can be found in the URL when viewing the folder in the Box web application. |
No output schema declared.
No examples provided.
permanently_delete_web_link Permanently Delete Web Link ~60
Permanently deletes a web link that is currently in the trash, removing it from Box entirely. This action is irreversible and cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| web_link_id | string | yes | The unique identifier of the web link to permanently delete from the trash. |
No output schema declared.
No examples provided.
promote_file_version Promote File Version ~144
Promotes an older version of a file to the top of its version history by creating a new copy with the same contents, hash, etag, and name. Suitable for file formats like PDF, DOC, and PPTX, but not for Box Notes.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | The unique identifier of the file whose version you want to promote. Visible in the file's URL in the Box web application. |
| id | string | – | The unique identifier of the specific file version to promote to the top of the version history. |
| type | string | – | The resource type being promoted. Must be set to 'file_version' to indicate a file version promotion. |
No output schema declared.
No examples provided.
query_items_by_metadata Query Items by Metadata ~270
Search for files and folders using SQL-like syntax against a specific metadata template. Use the `fields` attribute to include additional metadata fields in the results.
| Name | Type | Req | Description |
|---|---|---|---|
| ancestor_folder_id | string | – | The ID of the folder to scope the query to. Use `0` to search across all accessible folders, or provide a specific folder ID to restrict results to that folder and its subfolders. |
| from | string | – | The metadata template to query against, specified as `scope.templateKey`. Built-in Box-provided classification templates are not supported. |
| limit | integer | – | The maximum number of results to return in a single request, between 0 and 100. This is an upper boundary and does not guarantee a minimum number of results. |
| order_by | array | – | An ordered list of metadata template fields and sort directions to apply to the results. All items in the array must use the same sort direction. |
| query | string | – | A SQL-like logical expression used to filter items by their metadata field values. Use named placeholders (e.g., `:paramName`) to reference values defined in `query_params`. |
| query_params | object | – | A key-value map of named parameters referenced in the `query` expression. Each value's type must match the corresponding metadata template field type. |
No output schema declared.
No examples provided.
remove_file_classification Remove File Classification ~82
Removes any existing security classification from a specified file. This permanently strips the classification metadata, and can also be called using an explicit enterprise ID in the endpoint path.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | The unique identifier of the file from which the classification will be removed. The file ID can be found in the URL when viewing the file in the Box web application. |
No output schema declared.
No examples provided.
remove_file_shared_link Remove File Shared Link ~158
Removes an existing shared link from a file, revoking any previously granted public or shared access. Returns the updated file metadata with the shared link field cleared.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | yes | A comma-separated list of fields to include in the response. Must include 'shared_link' to confirm the shared link has been removed and retrieve the updated link state. |
| file_id | string | yes | The unique identifier of the file from which the shared link will be removed. The file ID can be found in the URL when viewing the file in the Box web application. |
| shared_link | object | – | Set this field to null to remove the shared link from the file. Omitting this field or providing any non-null value will not remove the link. |
No output schema declared.
No examples provided.
remove_file_skills_cards Remove File Skills Cards ~83
Removes all Box Skills cards metadata from a specified file. This clears any AI-generated skill annotations (such as transcripts, topics, or faces) associated with the file.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | The unique identifier of the file from which Box Skills cards will be removed. The file ID can be found in the file's URL in the Box web application. |
No output schema declared.
No examples provided.
remove_file_watermark Remove File Watermark ~66
Removes an existing watermark from a specified file in Box. Use this to revoke watermark protection previously applied to a file.
| Name | Type | Req | Description |
|---|---|---|---|
| file_id | string | yes | The unique identifier of the file from which the watermark will be removed. Found in the file's URL in the Box web application. |
No output schema declared.
No examples provided.
remove_folder_classification Remove Folder Classification ~70
Removes any existing security classification from a specified folder. This operation clears all classification metadata applied via the enterprise security classification schema.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | string | yes | The unique identifier of the folder from which the classification will be removed. The root folder of a Box account is always represented by ID '0'. |
No output schema declared.
No examples provided.
What is the com.mcparmory/box MCP server?
com.mcparmory/box is an MCP server listed in the public MCP registry as com.mcparmory/box. Manage files, folders, and team collaboration with access controls. This page covers its container image (ghcr.io/mcparmory/box:1.0.5).
Is the com.mcparmory/box MCP server safe to use?
com.mcparmory/box scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/box MCP server expose?
com.mcparmory/box exposes 246 tools: get_file, restore_file, update_file, delete_file, list_file_app_item_associations, and 241 more. Their descriptions and schemas cost roughly 34,690 tokens of context every time the server is loaded.
Is the com.mcparmory/box MCP server still maintained?
com.mcparmory/box is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.