Validate a standard write payload against optional fields_get metadata
AI agents call validate_write 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 performs read-only validation and schema inspection of a write payload using metadata. It examines data structure and constraints without executing the write operation or modifying any state. Validation tools are informational and have no side effects—they belong in the Read category.
From the tool's definition Tool name 'validate_write' and description 'Validate a standard write payload against optional fields_get metadata' indicate a validation/inspection operation.
Attacks that exploit this kind of access
Validate a standard write payload against optional fields_get metadata. 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 validate_write: 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.
validate_write 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 validate_write 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 validate_write. 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.
validate_write is provided by the Odoo MCP Server MCP server (pypi:odoo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.