How ERPeek protects your Odoo
Every interaction between the AI agent and your live Odoo passes through a mandatory security gateway. Here's exactly how it works, no hand-waving.
The MCP security gateway
The ERPeek MCP Gateway is a dedicated service that sits between the AI agent and your Odoo instance. Every data query and every write goes through it - there is no fallback and no direct XML-RPC access. The only other access is a read-only, audit-logged browser view the agent can use to look at Odoo screens the way you do; it can never modify anything.
Every request is inspected against your project's write policy before it reaches Odoo. If the gateway is unavailable, operations fail closed, they don't fall through to an unprotected path.
Per-project write policies
You control exactly what the agent can do in your Odoo, on a per-project basis. The default is the most secure option: read-only.
The agent can read records but cannot create, update, or delete anything. Zero write risk.
Enable create, update, or delete individually. Restrict to specific models (e.g., only sale.order and res.partner). Set batch limits (max records per write, max operations per batch).
Access to user/accounting/HR records and system configuration models (ir.*, base.*) requires separate, explicit opt-in, they are off by default.
The hard floor
Some operations are always blocked, regardless of your write policy. No setting can unlock them.
| Operation | Status |
|---|---|
| sudo() / elevated privilege | Always blocked |
| Raw SQL (execute_kw, _sql) | Always blocked |
| Module uninstall | Always blocked |
| Dunder methods (__*) | Always blocked |
Module install/upgrade is available as a separate opt-in in project settings, clearly labeled as highest-risk.
Credential security
- Odoo credentials are encrypted at rest using AES-256-GCM
- Credentials are never written to logs or error messages
- Credentials are never sent to the LLM, the agent sees only the data it retrieves, not how it authenticated
- Connections to your Odoo are encrypted with TLS when your instance is served over HTTPS, which we strongly recommend
Browsing your Odoo inside ERPeek
The Browser pane lets you open your own Odoo without leaving ERPeek. To reach your screen, the pages travel through ERPeek's servers. Here is what that does and does not mean.
- Nothing is stored: your Odoo pages pass through and are gone. ERPeek keeps no copy of any page, form, file or report you open
- No page content, form data, password or Odoo session is ever written to logs or error messages
- The passage only ever leads to the Odoo addresses connected to your project. ERPeek is not a general proxy and cannot be pointed anywhere else
- You sign in to Odoo as yourself, with your own browser and password manager. ERPeek never stores your Odoo password
- The AI sees only what you point at. It never watches your screen, and it never writes through the Odoo interface
Monitoring and fail-safe
- Gateway health is checked every 5 minutes with a full protocol-level probe
- Consecutive failures trigger an automatic alert (Sentry, fatal level)
- Docker auto-restart ensures the gateway recovers from crashes
- If the gateway is unreachable, all live-Odoo operations fail closed
Data handling and compliance
Security is one piece of the picture. For the full details on data residency, retention windows, secret handling, audit trails, and deletion flow, see our dedicated documentation: