AI agents call odoo_get_record_summary to retrieve information from Odooclaw without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_record_summary' strongly suggests a data retrieval operation that queries and returns a summary of an existing record without modifying or deleting it. This is consistent with Read category tools. While the empty description limits certainty, the naming convention and the presence of other CRUD/action tools in the server context support this classification.
From the tool's definition Tool name 'odoo_get_record_summary' indicates retrieval of summary data from records. The 'get' prefix conventionally signals read-only query operations. The tool description is empty, which reduces confidence slightly.
Attacks that exploit this kind of access
odoo_get_record_summary. It is categorised as a Read tool in the Odooclaw MCP Server, which means it retrieves data without modifying state.
Register the Odooclaw MCP server in PolicyLayer and add a rule for odoo_get_record_summary: 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 Odooclaw. Nothing to install.
odoo_get_record_summary 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 odoo_get_record_summary 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 odoo_get_record_summary. 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.
odoo_get_record_summary is provided by the Odooclaw MCP server (nicolasramos/odooclaw-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 →