Box Metadata (BYOK)

Box Metadata (BYOK) — connector documentation

• MCP endpoint: https://byok-box-metadata.connectorbay.com/mcp
• REST API: POST https://byok-box-metadata.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-box-metadata.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Box Metadata developer token or OAuth access token (developer tokens expire quickly), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-box-metadata.connectorbay.com/health · Tool schemas: https://byok-box-metadata.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-box-metadata · agent@connectorbay.com

What Box Metadata (BYOK) is for

Box Metadata (BYOK) lets an AI assistant read your own Box Metadata data through the Box Metadata API with a key you supply (developer token or OAuth access token (developer tokens expire quickly)). Read-only: 8 tools (list_enterprise_templates, list_global_templates, get_template_by_name, get_template_by_id, list_classifications, list_cascade_policies, list_taxonomies, list_taxonomy_nodes). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.box.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Box Metadata. Box Metadata and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which metadata templates does our Box account define?"
• "Which global Box metadata templates exist?"
• "What fields does Box metadata template 'contract' have?"
• "What is Box metadata template t-1?"
• "Which security classification labels does our Box account use?"
• "Which metadata cascade policies apply to Box folder 0?"

What it does

• list_enterprise_templates: List the metadata templates your enterprise defined, with key, display name and the fields of each template (field keys, types, descriptions, options).
• list_global_templates: List the metadata templates Box provides to every account (for example properties and box skills cards) with their fields.
• get_template_by_name: Get one metadata template by scope and key, with all its fields, field types, options and taxonomy links.
• get_template_by_id: Get one metadata template by its id, with all its fields, field types and options.
• list_classifications: List the security classification labels defined for the enterprise (names and ids), as stored in the classification metadata template.
• list_cascade_policies: List the metadata cascade policies of a folder: which template is applied automatically to everything inside it.
• list_taxonomies: List the metadata taxonomies in a namespace with key, display name and level definitions (taxonomy trees used by template fields).
• list_taxonomy_nodes: List the nodes (values) of one metadata taxonomy with level, parent and path, optionally filtered by text, level or parent node.

BYOK key

You bring your own Box Metadata developer token or OAuth access token (developer tokens expire quickly) (https://app.box.com/developers/console). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.box.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://developer.box.com/reference/ (the API this connector calls, with a BYOK key)

Live from the Box Metadata API (api.box.com) with a BYOK key; documentation: https://developer.box.com/reference/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Box Metadata. Box Metadata and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Box Metadata account.

Built for: Worldwide. Languages: English.

Box Metadata (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Box Metadata (BYOK) is. Box Metadata (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Box Metadata data: Read your Box metadata templates and their fields, security classifications, taxonomies and cascade policies with your own developer or OAuth token. You bring your own Box Metadata developer token or OAuth access token (developer tokens expire quickly); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Box Metadata call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.box.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Box Metadata rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Box Metadata receives. The request we make on your behalf, including the key and the arguments, under Box Metadata's own terms and privacy policy. Box Metadata acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Box Metadata gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Box Metadata data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Box Metadata (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Box Metadata at any time to end all access.

Children. Box Metadata (BYOK) is a general-audience service operated by the adult using the assistant, under Box Metadata's own age rules.

Changes. We will post changes here with a new effective date.

Box Metadata (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Box Metadata (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Box Metadata (BYOK) provides: Read your Box metadata templates and their fields, security classifications, taxonomies and cascade policies with your own developer or OAuth token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Box Metadata credentials and only access data you are allowed to access. Box Metadata's terms apply to your use of Box Metadata; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Box Metadata. Box Metadata and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Box Metadata returns, lightly trimmed; it may be incomplete, delayed or changed by Box Metadata. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Box Metadata account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Box Metadata's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Box Metadata may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Box Metadata key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Box Metadata takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-box-metadata

Box Metadata (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-box-metadata.connectorbay.com/mcp
• REST API: https://byok-box-metadata.connectorbay.com/openapi.json
• Live status: https://byok-box-metadata.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Box Metadata (BYOK) never asks for them.