Read one ir.attachment record: metadata always, base64 content when it
AI agents call read_attachment to retrieve information from Odoo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves attachment metadata and optionally base64-encoded content from Odoo's ir.attachment model. This is a read-only operation with no side effects, no data modification, no code execution, and no destructive capability. While attachments could theoretically contain sensitive information, the act of reading them is a standard query operation.
From the tool's definition Tool name is 'read_attachment' and description states 'Read one ir.attachment record: metadata always, base64 content when it' — the verb 'read' and retrieval-only semantics indicate data retrieval without modification.
Attacks that exploit this kind of access
Read one ir.attachment record: metadata always, base64 content when it. It is categorised as a Read tool in the Odoo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Odoo MCP Server MCP server in PolicyLayer and add a rule for read_attachment: 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 MCP Server. Nothing to install.
read_attachment 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 read_attachment 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 read_attachment. 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.
read_attachment is provided by the Odoo MCP Server MCP server (pypi:odoo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.