ToolTrust
A4/100
jfrog

jfrog-mcp-jfrog

mcp0.0.1

@jfrog

Model Context Protocol (MCP) Server for the JFrog Platform API, enabling repository management, build tracking, release lifecycle management, and more.

By jfrog | 53 findings | Scanned 6/22/2026 | tooltrust-scanner/v0.3.19 | 115

7 Low46 Info

Risk Summary

Safe With Normal Controls

Dep Visibility is the main signal, but overall risk remains within an acceptable range.

Potential impact: This finding indicates the tool should be reviewed before it is trusted.

Recommended action: No high-risk findings were detected in this scan, but you should still apply least-privilege defaults and rescan after changes.

Suggested policy: keep this tool behind manual approval, do not allow unattended runs, and re-scan after narrowing risky permissions.

Security Findings (53)

  • LowAS-011

    ℹ️Missing Rate-Limit / Timeout ×5

    tool performs network or execution operations but declares no rate-limit, timeout, or retry configuration

    jfrog_create_local_repositoryjfrog_create_virtual_repositoryjfrog_create_projectjfrog_execute_aql_queryjfrog_get_package_info

    Fix: Declare explicit rate-limit, timeout, and retry configuration for all network and execution tools. Implement exponential back-off and surface resource state to the calling agent.

  • LowAS-002

    ⚠️Excessive Permissions ×2

    input schema exposes 65 properties (threshold: 10)

    jfrog_create_remote_repository

    input schema exposes 24 properties (threshold: 10)

    jfrog_create_virtual_repository

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • InfoAS-014

    ℹ️Dependency Inventory Unavailable ×31

    Tool did not expose metadata.dependencies or repo_url, so supply-chain coverage is limited.

    jfrog_check_availabilityjfrog_create_local_repositoryjfrog_create_remote_repositoryjfrog_create_virtual_repositoryjfrog_set_folder_propertyjfrog_list_repositoriesjfrog_list_buildsjfrog_get_specific_buildjfrog_list_runtime_clustersjfrog_get_runtime_specific_clusterjfrog_list_running_imagesjfrog_list_environmentsjfrog_list_projectsjfrog_create_projectjfrog_get_specific_projectjfrog_execute_aql_queryjfrog_get_package_infojfrog_get_package_versionsjfrog_get_package_version_vulnerabilitiesjfrog_get_vulnerability_infojfrog_get_package_curation_statusjfrog_list_permission_targetsjfrog_get_permission_targetjfrog_create_permission_targetjfrog_update_permission_targetjfrog_delete_permission_targetjfrog_get_permission_resourcejfrog_update_permission_resourcejfrog_replace_permission_resourcejfrog_delete_permission_resourcejfrog_get_artifacts_summary

    Fix: Review and remediate the identified issue.

  • InfoAS-002

    ⚠️Excessive Permissions ×13

    declared capabilities: code/command execution, filesystem access, environment variables

    jfrog_create_local_repositoryjfrog_create_virtual_repository

    declared capabilities: code/command execution, network access, filesystem access, environment variables

    jfrog_create_remote_repository

    declared capabilities: filesystem access

    jfrog_set_folder_propertyjfrog_create_permission_targetjfrog_update_permission_targetjfrog_delete_permission_targetjfrog_update_permission_resourcejfrog_delete_permission_resourcejfrog_get_artifacts_summary

    declared capabilities: code/command execution, filesystem access

    jfrog_create_project

    declared capabilities: code/command execution, network access, database access

    jfrog_execute_aql_query

    declared capabilities: network access

    jfrog_get_package_info

    Fix: Tool requests broad permissions (exec/fs/network). Validate input parameters using Enums where possible, and restrict file system operations to explicit allowed directories.

  • InfoAS-010

    🔑Insecure Secret Handling ×2

    input parameter "password" accepts a credential (informational; not evidence of insecure handling)

    jfrog_create_remote_repository

    input parameter "enableTokenAuthentication" accepts a credential (informational; not evidence of insecure handling)

    jfrog_create_remote_repository

    Fix: Avoid accepting raw credentials as input parameters. Use secret managers (e.g. 1Password CLI, AWS Secrets Manager) and ensure credentials are never logged or stored in agent traces.

Scan this tool yourself

Reproduce this audit locally, integrate into CI, or let your agent audit its own tools.

Install once, then scan any MCP server:

$ curl -sfL https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-scanner/main/install.sh | bash
$ tooltrust-scanner scan --server "npx -y jfrog-mcp-jfrog"

Adjust the package name if your npm registry name differs from the tool ID. View source

Add badge to your README

Copy this Markdown to show your ToolTrust grade on GitHub.

[![ToolTrust Grade A](https://raw.githubusercontent.com/AgentSafe-AI/tooltrust-directory/main/docs/badges/grade-a.svg)](https://github.com/AgentSafe-AI/tooltrust-directory)