Execute the rollback plan for action_log[index]. The reversal
AI agents call rollback_apply to permanently remove resources in Mureo — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Rollback operations revert prior changes in a way that cannot be trivially undone again; in the context of Google Ads campaign management, this could delete or overwrite ads, ad groups, or settings that were previously created or modified. The most severe applicable category is Destructive due to the irreversible nature of reversals. Confidence is slightly reduced because the description is truncated and incomplete.
From the tool's definition "Execute the rollback plan for action_log[index]. The reversal" — applies a reversal/rollback of a logged action, which irreversibly undoes previously applied changes to ad campaigns, ad groups, or ads
Documented attack patterns abuse exactly the kind of access rollback_apply gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mureo, and nothing reaches the server without passing your rules. This is the rule we recommend for rollback_apply:
{
"version": "1",
"default": "deny",
"hide": [
"rollback_apply"
]
}rollback_apply disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Execute the rollback plan for action_log[index]. The reversal. It is categorised as a Destructive tool in the Mureo MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mureo MCP server in PolicyLayer and add a rule for rollback_apply: 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 Mureo. Nothing to install.
rollback_apply 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_apply 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_apply. 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_apply is provided by the Mureo MCP server (logly/mureo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mureo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
185 Mureo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.