Get field definitions for Odoo model
AI agents call odoo_fields_get to retrieve information from Odoo XML-RPC MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves structural metadata (field definitions) from an Odoo model. It has no side effects, does not create, modify, or delete data, and does not execute arbitrary operations. It is a straightforward data retrieval operation with minimal risk even if misused by an agent, as it only exposes schema information already accessible within the Odoo instance.
From the tool's definition Tool name 'odoo_fields_get' and description 'Get field definitions for Odoo model' indicate a retrieval operation that queries metadata without modifying data.
Attacks that exploit this kind of access
Get field definitions for Odoo model. It is categorised as a Read tool in the Odoo XML-RPC MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Odoo XML-RPC MCP Server MCP server in PolicyLayer and add a rule for odoo_fields_get: 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 XML-RPC MCP Server. Nothing to install.
odoo_fields_get 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_fields_get 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_fields_get. 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_fields_get is provided by the Odoo XML-RPC MCP Server MCP server (odoo-dgoo2308/xml-rpc-odoo-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 →