Low Risk

ai_usage_log_export

Export billing ledger rows as CSV for a tenant + date range.

How to control ai_usage_log_export ↓

What ai_usage_log_export does on Odoo Claude MCP

AI agents call ai_usage_log_export 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.

Low Risk

Why ai_usage_log_export needs a policy

This tool reads and exports billing/financial data (ledger rows) as CSV. It is a data retrieval operation with no side effects—it does not move money or modify records. However, the billing ledger contains sensitive financial information, so misuse (e.g., exfiltrating tenant billing data) carries medium severity.

From the tool's definition Export billing ledger rows as CSV for a tenant + date range

Documented attack patterns abuse exactly the kind of access ai_usage_log_export gives an agent:

How to control ai_usage_log_export

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 ai_usage_log_export:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "ai_usage_log_export": {}
  }
}

ai_usage_log_export is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Odoo Claude MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about ai_usage_log_export

What does the ai_usage_log_export tool do? +

Export billing ledger rows as CSV for a tenant + date range. It is categorised as a Read tool in the Odoo Claude MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ai_usage_log_export? +

Register the Odoo Claude MCP server in PolicyLayer and add a rule for ai_usage_log_export: 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.

What risk level is ai_usage_log_export? +

ai_usage_log_export is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ai_usage_log_export? +

Yes. Add a rate_limit block to the ai_usage_log_export 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.

How do I block ai_usage_log_export completely? +

Set action: deny in the PolicyLayer policy for ai_usage_log_export. 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.

What MCP server provides ai_usage_log_export? +

ai_usage_log_export 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.

Enforce policy on every Odoo Claude MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.