odoo_disconnect
Remove an Odoo connection.
This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/odoo-disconnect.md
What odoo_disconnect does on Odoo Claude MCP
AI agents call odoo_disconnect to permanently remove resources in Odoo Claude MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why odoo_disconnect is rated Critical
Removing a connection is a destructive action that cannot be undone without reconfiguring the connection. If misused, an AI agent could remove active Odoo connections, disrupting access to the instance. Severity is medium because it affects connectivity/configuration rather than business data directly, but could cause service disruption.
From the tool's definition "Remove an Odoo connection" — the word 'Remove' indicates an irreversible deletion of a configured connection
Attacks that exploit this kind of access
The rule that runs odoo_disconnect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Odoo Claude MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For odoo_disconnect, this is the rule to start with:
odoo_disconnect is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every odoo_disconnect call is checked against it from then on.
Questions about odoo_disconnect
Remove an Odoo connection. It is categorised as a Destructive tool in the Odoo Claude MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for odoo_disconnect: 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 Odoo Claude MCP. Nothing to install.
odoo_disconnect 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_disconnect 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_disconnect. 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_disconnect is provided by the Odoo Claude MCP server (rosenvladimirov/odoo-claude-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Odoo Claude, and thousands of servers like it.
Across the catalogue