Read records with security using global authentication
AI agents call odoo.read to retrieve information from Panda 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 retrieves data from Odoo instances without creating, modifying, deleting, or executing code. The security context ('with security using global authentication') is a protective measure, not an indication of heightened risk. Read operations have minimal blast radius as they cannot alter system state. Low severity is appropriate for query-only operations even in business-critical systems.
From the tool's definition Tool name 'odoo.read' combined with description 'Read records with security using global authentication' clearly indicates data retrieval without modification or deletion. The verb 'read' and phrase 'read records' explicitly denote a query operation.
Documented attack patterns abuse exactly the kind of access odoo.read gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Panda Odoo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for odoo.read:
{
"version": "1",
"default": "deny",
"tools": {
"odoo.read": {}
}
} odoo.read 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.
Read records with security using global authentication. It is categorised as a Read tool in the Panda Odoo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Panda Odoo MCP Server MCP server in PolicyLayer and add a rule for odoo.read: 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 Panda Odoo MCP Server. Nothing to install.
odoo.read 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.read 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.read. 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.read is provided by the Panda Odoo MCP Server MCP server (pandeussilvae/mcp-odoo-panda). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Panda Odoo MCP Server, 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.
21 Panda Odoo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.