search_by_attribute
AI agents call search_by_attribute to retrieve information from Odoo Index MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a search operation on a code indexing system to retrieve Odoo code metadata. No evidence of side effects, modifications, deletion, execution, or financial impact. Classified as Read with confidence lowered slightly (0.85 instead of higher) due to empty description, but the server's documented purpose and naming convention of sibling tools strongly indicate read-only behavior.
From the tool's definition Tool name 'search_by_attribute' and server purpose describes 'search and retrieve details about Odoo code elements' with 'exact file locations'. Sibling tools include 'search_odoo_index', 'list_modules', 'get_item_details'—all read-only operations.
Attacks that exploit this kind of access
search_by_attribute. It is categorised as a Read tool in the Odoo Index MCP MCP Server, which means it retrieves data without modifying state.
Register the Odoo Index MCP server in PolicyLayer and add a rule for search_by_attribute: 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 Index MCP. Nothing to install.
search_by_attribute 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_by_attribute 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_by_attribute. 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_by_attribute is provided by the Odoo Index MCP server (letzdoo/odoo-indexer-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 →