Get the version history for a specific enrolled file.
AI agents call get_file_versions to retrieve information from Rockhopper MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical version information for a file without creating, modifying, deleting, or executing any operations. It is a read-only operation that queries existing data. The severity is low because accessing version history poses minimal risk—it provides metadata about past states without allowing changes to data or system resources.
From the tool's definition Tool description explicitly states 'Get the version history' with no modification capabilities mentioned. The verb 'get' and context of 'version history' indicate pure data retrieval.
Attacks that exploit this kind of access
Get the version history for a specific enrolled file. It is categorised as a Read tool in the Rockhopper MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rockhopper MCP Server MCP server in PolicyLayer and add a rule for get_file_versions: 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.
get_file_versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_file_versions 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 get_file_versions. 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.
get_file_versions 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →