AI agents use odoo_replace_contract_line to create or update resources in Odooclaw — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Odooclaw environment.
Based on the tool name, 'replace_contract_line' performs a write operation that modifies existing contract data. This is reversible (can be undone via other write operations or Odoo's audit trail), making it Write rather than Destructive. The medium severity reflects that contract modifications could affect business workflows, but the impact is localized to contract management.
From the tool's definition Tool name 'odoo_replace_contract_line' indicates it modifies contract line data within Odoo ERP. The verb 'replace' suggests data replacement/modification. No description provided to confirm exact behavior.
Attacks that exploit this kind of access
odoo_replace_contract_line. It is categorised as a Write tool in the Odooclaw MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Odooclaw MCP server in PolicyLayer and add a rule for odoo_replace_contract_line: 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_replace_contract_line is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the odoo_replace_contract_line 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_replace_contract_line. 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_replace_contract_line 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 →