Get list of installed Odoo modules.
AI agents call odoo_get_installed_modules to retrieve information from MCP Odoo Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about currently installed modules in an Odoo system. It performs no side effects, creates no data, modifies nothing, and cannot cause destructive changes. It is a simple informational query analogous to listing installed packages. While knowing which modules are installed could inform an attack strategy, the tool itself has negligible direct risk as it only reads metadata.
From the tool's definition Tool name 'odoo_get_installed_modules' and description 'Get list of installed Odoo modules' indicate a retrieval operation that queries the system state without modification, creation, or deletion.
Attacks that exploit this kind of access
Get list of installed Odoo modules. It is categorised as a Read tool in the MCP Odoo Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Odoo Server MCP server in PolicyLayer and add a rule for odoo_get_installed_modules: 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_get_installed_modules is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the odoo_get_installed_modules 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_get_installed_modules. 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_get_installed_modules 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 →