Return local Odoo source, base command, and tooling README context from environment variables.
AI agents call get_odoo_local_context 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 queries and retrieves environment-variable-stored configuration, source paths, and documentation metadata. It performs no state changes, does not execute code or commands, and does not modify data. It is purely informational retrieval, fitting the 'Read' category.
From the tool's definition Tool description states it 'Return[s]' context from environment variables—a retrieval operation with no modification or execution of code. The verb 'get' and 'return' indicate read-only access to configuration and documentation data.
Documented attack patterns abuse exactly the kind of access get_odoo_local_context 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 get_odoo_local_context:
{
"version": "1",
"default": "deny",
"tools": {
"get_odoo_local_context": {}
}
}get_odoo_local_context 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.
Return local Odoo source, base command, and tooling README context from environment variables. 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 get_odoo_local_context: 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.
get_odoo_local_context 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 get_odoo_local_context 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 get_odoo_local_context. 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.
get_odoo_local_context 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.