odoo_search

Search for record IDs matching a domain filter.

SERVEROdoo Claude MCP SOURCErosenvladimirov/odoo-claude-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rosenvladimirov-odoo-claude-mcp/odoo-search.md

WHAT IT DOES

What odoo_search does on Odoo Claude MCP

AI agents call odoo_search to retrieve information from Odoo Claude MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why odoo_search is rated Low

The tool performs a search operation to locate and return record IDs based on filter criteria. This is a read-only query with no capability to create, modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could only retrieve information it is already authorized to access via Odoo's permission model. Classified as Read with low severity.

From the tool's definition Tool name 'odoo_search' and description 'Search for record IDs matching a domain filter' indicate a query operation that retrieves data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs odoo_search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Odoo Claude MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For odoo_search, this is the rule to start with:

odoo_search Allowed

odoo_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "odoo_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Odoo Claude MCP, apply this rule, and every odoo_search call is checked against it from then on.

FAQ

Questions about odoo_search

What does the odoo_search tool do? +

Search for record IDs matching a domain filter. 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 odoo_search? +

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

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

Can I rate-limit odoo_search? +

Yes. Add a rate_limit block to the odoo_search 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 odoo_search completely? +

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

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

KEEP EXPLORING

More on Odoo Claude, and thousands of servers like it.

This server

All 246 Odoo Claude tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →