Home / Companies / JFrog / Blog / Post Details
Content Deep Dive

The Evolution of JFrog AI Catalog: Your AI Control Plane for Agentic Development

Blog post from JFrog

Post Details
Company
Date Published
Author
Guy Eshet, JFrog Senior Manager, Product Manager
Word Count
1,478
Company Posts That Month
6
Language
English
Hacker News Points
-
Post removed?
No
Summary

JFrog positions its expanded AI Catalog as an AI control plane designed to secure the Agentic Development Lifecycle, where coding agents dynamically assemble models, MCP servers, skills, plugins, hooks, rules, and agent packages from potentially unvetted sources. The company argues that traditional software security controls and signature-based scans cannot adequately detect emerging threats such as malicious MCP packages and skills, which can execute harmful instructions while evading known-malware detection. The platform stores AI assets as versioned, traceable artifacts in Artifactory and adds dedicated registries for MCP servers, skills, plugins, and agent packages, alongside semantic scanning intended to inspect an asset’s instructions and shadow-AI detection for unmanaged assets. JFrog also describes runtime policy enforcement through agent plugins and Agent Guard, which restrict asset installations and MCP or skill calls across coding environments such as Claude Code, Cursor, VS Code, OpenCode, and Codex. By integrating AI governance with its existing software supply-chain tooling, RBAC, and audit records, JFrog aims to ensure that enterprise agents can access only organization-approved AI assets without requiring a separate AI security system.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
MCP 12 No monthly metrics for this publish month.
AI Agents 1 No monthly metrics for this publish month.
AI Coding Assistant 1 No monthly metrics for this publish month.
Agent Plugins 1 No monthly metrics for this publish month.
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.