odoo_rollback_patch_safe
AI agents call odoo_rollback_patch_safe to permanently remove resources in Odooclaw — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'odoo_rollback_patch_safe' strongly suggests reverting a patch, which undoes or overwrites applied changes. While 'safe' in the name may imply some safeguards, a rollback operation is generally considered destructive as it irreversibly reverts state. The description is empty, which lowers confidence.
From the tool's definition Tool name contains 'rollback' and 'patch' — rollback implies reverting/undoing previously applied changes, which is typically irreversible or overwrites current state.
Attacks that exploit this kind of access
odoo_rollback_patch_safe. It is categorised as a Destructive tool in the Odooclaw MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Odooclaw MCP server in PolicyLayer and add a rule for odoo_rollback_patch_safe: 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 Odooclaw. Nothing to install.
odoo_rollback_patch_safe 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 odoo_rollback_patch_safe 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 odoo_rollback_patch_safe. 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.
odoo_rollback_patch_safe is provided by the Odooclaw MCP server (nicolasramos/odooclaw-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 →