New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

odoo_disconnect

Remove an Odoo connection.

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about odoo_disconnect

What does the odoo_disconnect tool do? +

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.

How do I enforce a policy on odoo_disconnect? +

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.

What risk level is odoo_disconnect? +

odoo_disconnect is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit odoo_disconnect? +

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.

How do I block odoo_disconnect completely? +

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.

What MCP server provides odoo_disconnect? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Odoo Claude's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.