Diagnose an Odoo model call without executing it
AI agents call diagnose_odoo_call 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 diagnostic analysis of Odoo calls without side effects. It retrieves or examines information about a potential call (parameters, structure, likely outcomes) without executing it or modifying any data. This is a pure read/inspection operation with no state changes, making it a Read category risk with low severity.
From the tool's definition Tool description states 'Diagnose an Odoo model call without executing it' - explicitly indicates no execution occurs, only analysis/diagnosis.
Attacks that exploit this kind of access
Diagnose an Odoo model call without executing it. 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 diagnose_odoo_call: 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.
diagnose_odoo_call 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 diagnose_odoo_call 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 diagnose_odoo_call. 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.
diagnose_odoo_call 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.