AI agents use odoo_create_helpdesk_ticket 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.
Creating a helpdesk ticket is a reversible write operation that adds a new record to the Odoo system. While it modifies state, tickets can be deleted or archived later. The lack of description prevents definitive assessment of whether it triggers side effects (email notifications, workflow automation) that might elevate severity, but creation itself is fundamentally a write action with medium severity given…
From the tool's definition Tool name 'odoo_create_helpdesk_ticket' indicates creation of a new helpdesk ticket record. The tool prefix 'odoo_create_' and the context of CRUD operations on an Odoo ERP system confirm this is a write operation that creates data.
Attacks that exploit this kind of access
odoo_create_helpdesk_ticket. 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: 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 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 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. 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 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 →