MCP Beta Tools
Beta tools available in the JFrog MCP Server on self-managed environments, and how to opt in or out.
A small set of JFrog MCP Server tools are released as Beta. When you register the MCP Server integration, beta_tools_approved defaults to false, which hides Beta tools from MCP clients. To use them, an administrator sets beta_tools_approved to true for the integration.
Using Beta tools requires accepting the JFrog Online Beta Agreement - MCP Server Beta Tools.
Beta Tools on Self-Managed Environments
The following table lists the Beta tools available in the JFrog MCP Server 1.0.x on self-managed environments, grouped by toolset. For full parameter details, see MCP Server Tools (1.0.x).
| Toolset | Tool | Description |
|---|---|---|
| Access: Tokens | access_tokens_create | Create a new access token. |
| Access: Tokens | access_tokens_list | List access tokens with filters. |
| OneModel | onemodel_graphql_query_execute | Query JFrog platform data via OneModel. |
| OneModel | onemodel_graphql_query_introspect | Introspect the OneModel GraphQL schema. |
Opt In to Beta Tools at Registration
To enable Beta tools when you register the MCP Server integration, add "beta_tools_approved": true to the request body of the POST .../platform-integrations/provision call. For the complete registration procedure, see Enable MCP Server Integration.
{
"beta_tools_approved": true
}Opt In or Out After Registration
To change the Beta tools setting on an existing integration, send a PATCH .../platform-integrations/current request with beta_tools_approved set to true (opt in) or false (opt out).
Opt in:
{
"beta_tools_approved": true
}Opt out:
{
"beta_tools_approved": false
}Frequently Asked Questions
This section provides answers to frequently asked questions.
FAQs
Q: Are Beta tools stable?
No. Beta tools are provided for early evaluation. Their names, parameters, and behavior can change in a later release without notice.
Q: Can I disable Beta tools after enabling them?
Yes. Send a PATCH .../platform-integrations/current request with "beta_tools_approved": false. MCP clients stop seeing Beta tools once the setting is applied.
Q: Why are some Beta tools listed in the JFrog SaaS documentation missing here?
Some Beta tools, such as the Workers tools that update or run a worker, require interactive user approval. The self-managed MCP Server runs without session state by default, which hides tools that require approval, even when beta_tools_approved is true.
Q: Do Beta tools bypass JFrog Platform permissions?
No. Beta tools follow the same JFrog Platform permission model as all other MCP Server tools. A user can only run a Beta tool for actions they are already authorized to perform on the platform.
Related Topics
Updated about 6 hours ago