Discard all uncommitted changes on an enrolled file, reverting it to the latest
AI agents call discard_changes to permanently remove resources in Rockhopper MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible operation that cannot be undone once executed. Discarding uncommitted changes permanently loses that work, meeting the definition of Destructive. The blast radius is high because an AI agent executing this without proper confirmation could cause significant loss of user work.
From the tool's definition Tool name is 'discard_changes' and description states it will 'Discard all uncommitted changes on an enrolled file, reverting it to the latest' — this irreversibly deletes/overwrites uncommitted work without recovery option.
Attacks that exploit this kind of access
Discard all uncommitted changes on an enrolled file, reverting it to the latest. It is categorised as a Destructive tool in the Rockhopper MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Rockhopper MCP Server MCP server in PolicyLayer and add a rule for discard_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.
discard_changes is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the discard_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 discard_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.
discard_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 →