Inspect Odoo core/addon source with AST and return a compact source map.
AI agents call inspect_odoo_source to retrieve information from Odoo Dev MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes existing source code from Odoo core/addons using abstract syntax tree (AST) parsing to generate a source map. There are no indications of writing, executing, deleting, or financial operations. It is a developer utility for code exploration and analysis, which is a classic Read category operation with minimal risk.
From the tool's definition Tool performs source code inspection and returns a 'compact source map' with no modification capability mentioned. The verb 'inspect' and the description's focus on reading and analyzing code ('AST') indicates a read-only operation.
Documented attack patterns abuse exactly the kind of access inspect_odoo_source gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Dev MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for inspect_odoo_source:
{
"version": "1",
"default": "deny",
"tools": {
"inspect_odoo_source": {}
}
}inspect_odoo_source is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Inspect Odoo core/addon source with AST and return a compact source map. It is categorised as a Read tool in the Odoo Dev MCP MCP Server, which means it retrieves data without modifying state.
Register the Odoo Dev MCP server in PolicyLayer and add a rule for inspect_odoo_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 Dev MCP. Nothing to install.
inspect_odoo_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 inspect_odoo_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 inspect_odoo_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.
inspect_odoo_source is provided by the Odoo Dev MCP server (mart337i/odoo-dev-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Odoo Dev MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 Odoo Dev MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.