AI agents use set_odoo_version 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.
The name 'set_' indicates a write operation that modifies state (likely the target Odoo version for development). Without a description, confidence is reduced. This appears to be configuration management rather than data creation/deletion, hence Write category. Severity is low because changing a development version preference has limited blast radius and is reversible.
From the tool's definition Tool name 'set_odoo_version' suggests modifying a configuration or state value. No description provided to confirm exact behavior.
Documented attack patterns abuse exactly the kind of access set_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 set_odoo_version:
{
"version": "1",
"default": "deny",
"tools": {
"set_odoo_version": {
"limits": [
{
"counter": "set_odoo_version_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_odoo_version 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.
set_odoo_version. 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 set_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.
set_odoo_version 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 set_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 set_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.
set_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.