AI agents use create_odoo_module to create or update resources in Odoo Dev MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Odoo Dev MCP environment.
This tool creates new Odoo modules (code artifacts), which is a reversible Write operation. While the description is empty and lowers confidence slightly, the name and server context strongly indicate module generation rather than execution or destructive action. Module creation can be undone by deletion, making it Write rather than Destructive.
From the tool's definition Tool name 'create_odoo_module' indicates it creates module artifacts. The server context shows sibling tools include 'create_odoo_model', 'create_odoo_view', 'create_owl_component', all in a module development workflow.
Documented attack patterns abuse exactly the kind of access create_odoo_module gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Dev MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_odoo_module:
{
"version": "1",
"default": "deny",
"tools": {
"create_odoo_module": {
"limits": [
{
"counter": "create_odoo_module_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_odoo_module stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create_odoo_module. It is categorised as a Write tool in the Odoo Dev MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Odoo Dev MCP server in PolicyLayer and add a rule for create_odoo_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 Odoo Dev MCP. Nothing to install.
create_odoo_module 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 create_odoo_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 create_odoo_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.
create_odoo_module is provided by the Odoo Dev MCP server (mart337i/odoo-dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Odoo Dev MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 Odoo Dev MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.