Rollback all Epic entries from a run.
AI agents call rollback to permanently remove resources in Carrier Accounting MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Rolling back all Epic entries from a run constitutes a bulk, potentially irreversible deletion/reversal of financial accounting records in Applied Epic. This touches financial data (insurance carrier statements, posted entries) and the blast radius is critical — an AI agent misusing this could wipe an entire batch of posted accounting entries, causing significant financial and operational damage.
From the tool's definition 'Rollback all Epic entries from a run' — mass reversal of posted accounting entries in Applied Epic, which is irreversible in practice and affects financial records at scale.
Attacks that exploit this kind of access
Rollback all Epic entries from a run. It is categorised as a Destructive tool in the Carrier Accounting MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Carrier Accounting MCP server in PolicyLayer and add a rule for rollback: 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 Carrier Accounting MCP. Nothing to install.
rollback 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 rollback 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 rollback. 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.
rollback is provided by the Carrier Accounting MCP server (pramodmisra/carrier-accounting-mcp). 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 →