// SCAN REPORT

Odoo MCP Server

38 tools. 6 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 26 Jun 2026

6 can modify or destroy data

32 read-only

38 tools total

Community server · catalogue entry verified 26/06/2026

How to control Odoo MCP Server ↓

TOOL MAP

What Odoo MCP Server exposes to your agents

Read (32) Write / Execute (5) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Odoo MCP Server tools

Destructive · Medium cancel_async_task Cancelling a background task is an irreversible action — once cancelled, the task's execution is terminated and cannot be resumed. Execute · Critical execute_method This tool allows execution of custom methods on Odoo models without specifying constraints on what methods can be called. Write · High execute_approved_write This tool executes a write operation on an Odoo ERP system. Write · Medium chatter_post Posting to Chatter creates new communication records reversibly (messages can be deleted/archived).

6 of Odoo MCP Server's 38 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Odoo MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Odoo MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "cancel_async_task": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "execute_approved_write": {
    "limits": [
      {
        "counter": "execute_approved_write_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "build_domain": {
    "limits": [
      {
        "counter": "build_domain_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Odoo MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ODOO →

Instant setup, no code required.

FULL CATALOGUE

All 38 Odoo MCP Server tools

DESTRUCTIVE 1 tools

Destructive cancel_async_task Cancel a pending or running background task

EXECUTE 1 tools

Execute execute_method Execute a custom method on an Odoo model

WRITE 4 tools

Write execute_approved_write Execute a previously previewed and confirmed standard write Write chatter_post chatter_post Write preview_write Preview create, write, or unlink without executing it Write submit_async_task Run an allowlisted long-running read operation in the background

READ 32 tools

Read build_domain Build a validated Odoo domain from structured conditions Read index_knowledge Fetch a bounded slice of records and build a local BM25 knowledge index Read schema_catalog Build and cache a bounded Odoo model schema catalog Read accounting_health_across_instances AR/AP aging fanned out across instances — the partner-network sweep Read accounting_health_summary Open receivable/payable item counts and draft invoice backlog Read aggregate_across_instances Read-only aggregate fanned out across instances with combined grand totals Read aggregate_records aggregate_records Read business_pack_report Report expected modules, models, and safe discovery calls for a business pack Read diagnose_access Diagnose ACL and record-rule visibility for an Odoo model Read diagnose_odoo_call Diagnose an Odoo model call without executing it Read fit_gap_report Classify Odoo requirements into fit/gap implementation buckets Read get_async_task Poll a background task Read get_model_fields Get field metadata for a specific Odoo model Read get_odoo_profile Read a bounded profile of the connected Odoo environment Read health_check Report this MCP server Read inspect_model_relationships Inspect model relationships and required field metadata Read knowledge_stats Report local knowledge index sizes and document budget Read list_async_tasks List recent background tasks newest-first Read list_instances List configured Odoo instance names without credentials Read list_models List Odoo models with optional name filtering Read read_attachment Read one ir.attachment record: metadata always, base64 content when it Read read_record Read a single Odoo record by model and ID Read receivable_payable_aging Aged receivable/payable report bucketed by days overdue Read scan_addons_source Scan local Odoo addon source without importing addon code Read search_across_instances Read-only search fanned out across configured Odoo instances, merged and attributed Read search_employee Search for employees by name Read search_holidays Search for holidays within a date range Read search_knowledge Relevance-ranked local BM25 search over previously indexed records Read search_records search_records Read upgrade_risk_report Report Odoo upgrade and JSON-2 migration risks Read validate_write Validate a standard write payload against optional fields_get metadata Read generate_json2_payload Build a JSON-2 request preview without network access

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Odoo MCP Server

Can an AI agent delete data through the Odoo MCP Server MCP server? +

Yes. The Odoo MCP Server server exposes 1 destructive tools including cancel_async_task. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Odoo MCP Server? +

The Odoo MCP Server server has 4 write tools including execute_approved_write, chatter_post, preview_write. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Odoo MCP Server.

How many tools does the Odoo MCP Server MCP server expose? +

38 tools across 4 categories: Destructive, Execute, Read, Write. 32 are read-only. 6 can modify, create, or delete data.

How do I enforce a policy on Odoo MCP Server? +

Register the Odoo MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Odoo MCP Server tool call.

Deterministic rules across all 38 Odoo MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ODOO →

Instant setup, no code required.

38 Odoo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.