Detect the likely Odoo version from local evidence without changing current_version.
AI agents call detect_odoo_version to retrieve information from Odoo Dev MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries information about the Odoo version present in the local environment and reports findings. It performs no modifications, deletions, code execution, or financial operations. The explicit mention that it does not change current_version confirms its read-only nature.
From the tool's definition Tool performs detection/analysis of Odoo version from local evidence without modifying state. The description explicitly states it does this 'without changing current_version', confirming no side effects occur.
Documented attack patterns abuse exactly the kind of access detect_odoo_version 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 detect_odoo_version:
{
"version": "1",
"default": "deny",
"tools": {
"detect_odoo_version": {}
}
}detect_odoo_version is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Detect the likely Odoo version from local evidence without changing current_version. It is categorised as a Read tool in the Odoo Dev MCP MCP Server, which means it retrieves data without modifying state.
Register the Odoo Dev MCP server in PolicyLayer and add a rule for detect_odoo_version: 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.
detect_odoo_version 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 detect_odoo_version 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 detect_odoo_version. 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.
detect_odoo_version 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.