AI agents use create_odoo_view 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.
Creating Odoo views generates new configuration/UI data that can be modified or deleted later, making it a Write operation. Severity is high because misconfigured views in a development environment could affect multiple users or be propagated to production if not carefully managed. Confidence is reduced from 0.9 to 0.85 due to empty description, but the tool name and server context provide strong signals.
From the tool's definition Tool name 'create_odoo_view' with 'create' prefix indicates reversible creation of Odoo views, which are data structures defining UI layouts in Odoo applications.
Documented attack patterns abuse exactly the kind of access create_odoo_view 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_view:
{
"version": "1",
"default": "deny",
"tools": {
"create_odoo_view": {
"limits": [
{
"counter": "create_odoo_view_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_odoo_view 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_view. 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_view: 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_view 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_view 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_view. 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_view 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.