Uninstall an Odoo module by its technical name.
AI agents call odoo_uninstall_module to permanently remove resources in MCP Odoo Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Module uninstallation in Odoo is a destructive operation because it: (1) irreversibly removes module code and associated features, (2) typically removes or cascades deletion of related database tables and records, and (3) cannot be undone through standard operations—recovery requires system restoration.
From the tool's definition The tool uninstalls an Odoo module by its technical name. Uninstalling a module is an irreversible action that removes functionality, data structures, and potentially data from the Odoo system.
Attacks that exploit this kind of access
Uninstall an Odoo module by its technical name. It is categorised as a Destructive tool in the MCP Odoo Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Odoo Server MCP server in PolicyLayer and add a rule for odoo_uninstall_module: 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 MCP Odoo Server. Nothing to install.
odoo_uninstall_module 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_uninstall_module 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_uninstall_module. 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_uninstall_module is provided by the MCP Odoo Server MCP server (malvernbright/odoo-claude-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 →