Create a new project in the JFrog platform
AI agents use jfrog_create_project to create or update resources in JFrog MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JFrog MCP Server environment.
This tool creates a new project, which is a write operation that can be reversed (the project can be deleted). It is not a destructive action (irreversible deletion), nor does it involve financial transactions or code execution. The medium severity reflects that creating projects could consume platform resources or create organizational confusion, but the impact is localized to project management and reversible.
From the tool's definition Tool name includes 'create' and description states 'Create a new project in the JFrog platform', indicating reversible creation of a new resource rather than modification of existing data.
Documented attack patterns abuse exactly the kind of access jfrog_create_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JFrog MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for jfrog_create_project:
{
"version": "1",
"default": "deny",
"tools": {
"jfrog_create_project": {
"limits": [
{
"counter": "jfrog_create_project_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} jfrog_create_project stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new project in the JFrog platform. It is categorised as a Write tool in the JFrog MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the JFrog MCP Server MCP server in PolicyLayer and add a rule for jfrog_create_project: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches JFrog MCP Server. Nothing to install.
jfrog_create_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the jfrog_create_project rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for jfrog_create_project. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
jfrog_create_project is provided by the JFrog MCP Server MCP server (jfrog/mcp-jfrog). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from JFrog MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 JFrog MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.