AI agents call odoo_preview_view_patch to retrieve information from Odooclaw without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or display information about a view patch for inspection purposes, which is a read-only operation with no side effects. However, confidence is reduced to 0.6 because the description is empty, making it impossible to definitively confirm the tool does not modify or execute anything.
From the tool's definition Tool name 'odoo_preview_view_patch' suggests a preview operation. The verb 'preview' implies viewing/retrieving information about a patch rather than applying or modifying it.
Attacks that exploit this kind of access
odoo_preview_view_patch. It is categorised as a Read tool in the Odooclaw MCP Server, which means it retrieves data without modifying state.
Register the Odooclaw MCP server in PolicyLayer and add a rule for odoo_preview_view_patch: 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 Odooclaw. Nothing to install.
odoo_preview_view_patch 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_preview_view_patch 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_preview_view_patch. 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_preview_view_patch is provided by the Odooclaw MCP server (nicolasramos/odooclaw-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 →