Busca asientos contables con filtros
AI agents call search_journal_entries to retrieve information from Odoo Superior without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only search operation on journal entries in the Odoo accounting module. It retrieves or queries existing data with filter parameters but does not create, modify, or delete any records. This is a classic Read category operation with low severity since it only exposes data visibility.
From the tool's definition Tool name is 'search_journal_entries' and description states 'Busca asientos contables con filtros' (Search accounting entries with filters). This is a search/query operation that retrieves data without modification.
Attacks that exploit this kind of access
Busca asientos contables con filtros. It is categorised as a Read tool in the Odoo Superior MCP Server, which means it retrieves data without modifying state.
Register the Odoo Superior MCP server in PolicyLayer and add a rule for search_journal_entries: 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 Superior. Nothing to install.
search_journal_entries 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 search_journal_entries 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 search_journal_entries. 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.
search_journal_entries is provided by the Odoo Superior MCP server (nitram509/odoo-superior-mcp). 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 →