Get list of portal sale orders (/my/orders). Returns HTML page content.
AI agents call public_access_portal_orders to retrieve information from Odoo Claude MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing data (sale orders visible to the authenticated portal user) without side effects. It is a read-only operation that queries and displays information. While the data returned may contain sensitive business information (orders), the blast radius of misuse is limited to information disclosure about the user's own orders in a self-hosted Odoo instance, making it low severity.
From the tool's definition Tool returns a list of portal sale orders via GET-like retrieval; description states 'Get list...Returns HTML page content'. No modification, deletion, or execution of code is mentioned.
Documented attack patterns abuse exactly the kind of access public_access_portal_orders gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo Claude MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for public_access_portal_orders:
{
"version": "1",
"default": "deny",
"tools": {
"public_access_portal_orders": {}
}
} public_access_portal_orders 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.
Get list of portal sale orders (/my/orders). Returns HTML page content. It is categorised as a Read tool in the Odoo Claude MCP MCP Server, which means it retrieves data without modifying state.
Register the Odoo Claude MCP server in PolicyLayer and add a rule for public_access_portal_orders: 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 Claude MCP. Nothing to install.
public_access_portal_orders 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 public_access_portal_orders 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 public_access_portal_orders. 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.
public_access_portal_orders is provided by the Odoo Claude MCP server (rosenvladimirov/odoo-claude-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Odoo Claude 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.
180 Odoo Claude MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.