AI agents call list_payments to retrieve information from MCP-Odoo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'list_payments' follows the pattern of other Read tools on this server (list_customers, list_suppliers, list_vendor_bills). It retrieves payment records from an ERP system without modifying them. Severity is medium rather than low because payments constitute sensitive financial data; an agent with unrestricted access could exfiltrate comprehensive financial records, though this is read-only access.
From the tool's definition Tool name 'list_payments' indicates a retrieval operation. Sibling tools like 'list_accounting_entries', 'list_customers', 'list_invoices' are all Read operations.
Documented attack patterns abuse exactly the kind of access list_payments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Odoo, and nothing reaches the server without passing your rules. This is the rule we recommend for list_payments:
{
"version": "1",
"default": "deny",
"tools": {
"list_payments": {}
}
}list_payments 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.
list_payments. It is categorised as a Read tool in the MCP-Odoo MCP Server, which means it retrieves data without modifying state.
Register the MCP-Odoo MCP server in PolicyLayer and add a rule for list_payments: 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 MCP-Odoo. Nothing to install.
list_payments 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 list_payments 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 list_payments. 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.
list_payments is provided by the MCP-Odoo MCP server (yourtechtribe/mcp-odoo-for-finance). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Odoo, 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.
11 MCP-Odoo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.