获取Odoo模型的元数据信息，包括字段定义等
AI agents call get_odoo_model_metadata to retrieve information from Odoo 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 metadata about Odoo data models (field definitions, schema structure) without creating, modifying, or deleting any data. It is a read-only operation that queries system information. The low severity reflects minimal blast radius even if misused by an AI agent—worst case would be information disclosure of model structure, which is typically non-sensitive schema data.
From the tool's definition Tool name 'get_odoo_model_metadata' and description 'Gets metadata information of Odoo models, including field definitions' indicates retrieval of structural/schema information with no modification or side effects.
Attacks that exploit this kind of access
获取Odoo模型的元数据信息，包括字段定义等. It is categorised as a Read tool in the Odoo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Odoo MCP Server MCP server in PolicyLayer and add a rule for get_odoo_model_metadata: 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 MCP Server. Nothing to install.
get_odoo_model_metadata 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 get_odoo_model_metadata 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 get_odoo_model_metadata. 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.
get_odoo_model_metadata is provided by the Odoo MCP Server MCP server (kaikongbj/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 →