Scan local Odoo addon source without importing addon code
AI agents call scan_addons_source 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.
Scanning source code performs static analysis and retrieval of addon metadata or code structure without side effects. The explicit mention of 'without importing addon code' emphasizes that no execution occurs. This is a read-only operation with minimal blast radius—an AI agent using this tool can only discover information about addons, not modify, execute, or delete them.
From the tool's definition Tool name 'scan_addons_source' and description 'Scan local Odoo addon source without importing addon code' indicate passive inspection of addon files without execution, modification, or deletion.
Attacks that exploit this kind of access
Scan local Odoo addon source without importing addon code. 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 scan_addons_source: 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.
scan_addons_source 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 scan_addons_source 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 scan_addons_source. 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.
scan_addons_source 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.