Obtiene el historial de ventas de Odoo con fecha, hora y monto. Combina POS y eCommerce. Útil para analizar patrones temporales: días pico, horarios, mañana vs tarde. Las fechas están en UTC. Soporta paginación.
AI agents call getSalesHistory to retrieve information from Olivia without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Máximo de registros por fuente (default: 500) |
offset | number | — | Desde qué posición empezar (para paginación) |
source | string | — | Fuente: all, pos, ecommerce |
date_to | string | — | Fecha fin YYYY-MM-DD |
date_from | string | — | Fecha inicio YYYY-MM-DD |
Parameters from the server's own tool schema.
This tool retrieves and queries existing sales data from Odoo (dates, times, amounts) for analysis purposes. It has no side effects—no data is created, modified, deleted, or executed. This is a pure Read operation that fits the 'query/fetch' pattern. The low severity reflects that misuse would only expose historical business analytics data without enabling destructive or financial actions.
From the tool's definition Tool description states 'Obtiene el historial de ventas' (retrieves sales history) and explicitly supports pagination for querying historical data. No modification, deletion, or execution capabilities are described.
Attacks that exploit this kind of access
Obtiene el historial de ventas de Odoo con fecha, hora y monto. Combina POS y eCommerce. Útil para analizar patrones temporales: días pico, horarios, mañana vs tarde. Las fechas están en UTC. Soporta paginación. It is categorised as a Read tool in the Olivia MCP Server, which means it retrieves data without modifying state.
getSalesHistory accepts 5 parameters: limit, offset, source, date_to, date_from. The full parameter table on this page comes from the server's own tool schema.
Register the Olivia MCP server in PolicyLayer and add a rule for getSalesHistory: 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 Olivia. Nothing to install.
getSalesHistory 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 getSalesHistory 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 getSalesHistory. 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.
getSalesHistory is provided by the Olivia MCP server (@facusrod/olivia-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →