AI agents call odoo_scan_report_migration_issues 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 designed to identify and report issues during Odoo report migrations—a diagnostic/analytical function. Without explicit description, I cannot confirm whether it merely reads migration status or performs corrective actions. The 'migration' context alongside sibling tools like 'odoo_assist_report_migration' suggests this is a preparatory scanning step.
From the tool's definition Tool name contains 'scan' and 'migration_issues', suggesting it queries or analyzes data for migration problems rather than modifying systems. The 'scan' operation typically implies inspection or assessment without side effects.
Attacks that exploit this kind of access
odoo_scan_report_migration_issues. 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_scan_report_migration_issues: 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_scan_report_migration_issues 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_scan_report_migration_issues 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_scan_report_migration_issues. 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_scan_report_migration_issues 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 →