AI agents call odoo_get_view_by_xmlid 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.
This tool fetches view configuration data by XML ID from Odoo ERP, a standard querying operation with no side effects. The get_* pattern is characteristic of Read operations. While the empty description reduces confidence slightly, the naming convention is clear enough to classify with reasonable confidence. Blast radius is minimal—retrieving view metadata poses no risk if an AI agent calls it.
From the tool's definition Tool name 'odoo_get_view_by_xmlid' indicates retrieval of a view by its XML ID. The 'get' verb and absence of modification keywords (create, update, delete, apply) suggest a read-only operation.
Attacks that exploit this kind of access
odoo_get_view_by_xmlid. 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_get_view_by_xmlid: 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_get_view_by_xmlid 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_get_view_by_xmlid 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_get_view_by_xmlid. 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_get_view_by_xmlid 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 →