AI agents use create_order to create or update resources in Eyeot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Eyeot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | object | Yes | Request body |
Parameters from the server's own tool schema.
Creating a purchase order modifies business state by generating a binding commitment to buy goods/services, which has financial and operational consequences but remains reversible (orders can be cancelled or amended before fulfillment). This is Write rather than Execute (no arbitrary code/commands) or Financial (no immediate money movement, though it commits future payment).
From the tool's definition Tool name is 'create_order' with description 'Créer un bon de commande' (Create a purchase order). The 'create_' prefix and the verb 'Créer' indicate data creation. A purchase order is a reversible business document that can be modified or cancelled.
Risk signalsAccepts raw HTML/template content (body) · High parameter count (10 properties)
Attacks that exploit this kind of access
Créer un bon de commande. It is categorised as a Write tool in the Eyeot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_order accepts 1 parameter: body. Required: body. The full parameter table on this page comes from the server's own tool schema.
Register the Eyeot MCP server in PolicyLayer and add a rule for create_order: 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 Eyeot. Nothing to install.
create_order 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 create_order 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 create_order. 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.
create_order is provided by the Eyeot MCP server (https://erp.eyeot.fr/api/v1/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 →