Connect to Odoo using credentials from .env file. The .env file should contain ODOO_HOST, ODOO_DATABASE, ODOO_USERNAME, ODOO_API_KEY, and optionally ODOO_PORT and ODOO_PROTOCOL.
AI agents use odoo_connect_env to create or update resources in MCP Odoo Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Odoo Server environment.
An AI agent can call odoo_connect_env faster than any human can review — one bad instruction and it creates or modifies resources in MCP Odoo Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Connect to Odoo using credentials from .env file. The .env file should contain ODOO_HOST, ODOO_DATABASE, ODOO_USERNAME, ODOO_API_KEY, and optionally ODOO_PORT and ODOO_PROTOCOL. It is categorised as a Write tool in the MCP Odoo Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Odoo Server MCP server in PolicyLayer and add a rule for odoo_connect_env: 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_connect_env is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the odoo_connect_env 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_connect_env. 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_connect_env 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 →