Set properties on a folder in Artifactory, with optional recursive application
AI agents use jfrog_set_folder_property 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.
Setting properties on folders modifies metadata reversibly and can be undone by clearing or updating those properties. This is a Write operation, not Destructive (properties are not deleted permanently) or Execute (no code execution or external operations triggered).
From the tool's definition Tool description states "Set properties on a folder in Artifactory" — this is a create/modify operation on folder metadata.
Documented attack patterns abuse exactly the kind of access jfrog_set_folder_property 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_set_folder_property:
{
"version": "1",
"default": "deny",
"tools": {
"jfrog_set_folder_property": {
"limits": [
{
"counter": "jfrog_set_folder_property_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} jfrog_set_folder_property 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.
Set properties on a folder in Artifactory, with optional recursive application. 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_set_folder_property: 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_set_folder_property 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_set_folder_property 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_set_folder_property. 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_set_folder_property 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.