Get pending cell-level changes that have not been attributed to a
AI agents call get_unattributed_changes 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 query results about unattributed cell-level changes in the Rockhopper workspace. The 'get' prefix and action of fetching pending changes confirm it is a read-only operation with no side effects. It has low severity as it only exposes metadata about changes, not sensitive data operations or code execution.
From the tool's definition Tool name 'get_unattributed_changes' and description 'Get pending cell-level changes that have not been attributed to a' indicate retrieval of pending change metadata without modification or deletion of data.
Attacks that exploit this kind of access
Get pending cell-level changes that have not been attributed to a. 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_unattributed_changes: 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_unattributed_changes 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_unattributed_changes 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_unattributed_changes. 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_unattributed_changes 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 →