AI agents use odoo_create_helpdesk_ticket_from_partner 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.
This tool creates new helpdesk ticket records, which is a Write operation that modifies the system state reversibly. While the description is empty (lowering confidence slightly), the tool name unambiguously indicates a CREATE action. Severity is medium because creating tickets could spam the system or create unwanted support records, but the impact is limited to one data type and is reversible.
From the tool's definition Tool name indicates 'create' operation for helpdesk tickets from partner records. The 'create' verb and ticket generation functionality imply data creation/modification in the Odoo ERP system.
Attacks that exploit this kind of access
odoo_create_helpdesk_ticket_from_partner. 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_create_helpdesk_ticket_from_partner: 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_create_helpdesk_ticket_from_partner 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_create_helpdesk_ticket_from_partner 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_create_helpdesk_ticket_from_partner. 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_create_helpdesk_ticket_from_partner 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 →