create_version · Rockhopper MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_version does on Rockhopper MCP Server

AI agents use create_version to create or update resources in Rockhopper MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rockhopper MCP Server environment.

WHY IT NEEDS A POLICY

Why create_version needs a policy

This tool creates a new version (commits changes) in the Rockhopper workspace. While it modifies the file version history, it does not irreversibly delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or run external operations (Execute). The changes are reversible through version control mechanisms (can be reverted or amended in subsequent versions).

From the tool's definition Tool description states "Commit the current uncommitted changes on an enrolled file as a new version." The term "commit" and "new version" indicate this creates/modifies data in the version control system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_version Rate-limited

create_version 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_version": {
      "limits": [
        {
          "counter": "create_version_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Rockhopper MCP Server, so you can run agents against it safely.

FAQ

Questions about create_version

What does the create_version tool do? +

Commit the current uncommitted changes on an enrolled file as a new version. It is categorised as a Write tool in the Rockhopper MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_version? +

Register the Rockhopper MCP Server MCP server in PolicyLayer and add a rule for create_version: 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 Rockhopper MCP Server. Nothing to install.

What risk level is create_version? +

create_version is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_version? +

Yes. Add a rate_limit block to the create_version 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.

How do I block create_version completely? +

Set action: deny in the PolicyLayer policy for create_version. 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.

What MCP server provides create_version? +

create_version is provided by the Rockhopper MCP Server MCP server (rockhopper-co/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.