Get the change history for a specific cell in an enrolled file.
AI agents call get_cell_history 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 information about cell changes, which is a read-only query operation. It does not create, modify, delete, or execute any actions—it only fetches existing version history data. The low severity reflects minimal blast radius even if an AI agent misuses this; the worst outcome would be unauthorized viewing of historical cell changes within an enrolled file.
From the tool's definition Tool name is 'get_cell_history' and description states 'Get the change history for a specific cell in an enrolled file.' The verb 'Get' and the read-only nature of retrieving historical data indicate no modification or side effects.
Attacks that exploit this kind of access
Get the change history for a specific cell in an 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_cell_history: 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_cell_history 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_cell_history 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_cell_history. 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_cell_history 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 →