AI agents use accept_quote 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 |
|---|---|---|---|
quote_id | string | Yes | (path parameter) |
Parameters from the server's own tool schema.
This tool updates the status of a quote to 'accepted', which is a reversible state change (Write). While it has business implications (moving a sales opportunity forward), it does not directly move money or commit financial obligations — it merely records client acceptance. It could potentially be reversed by changing the quote status back.
From the tool's definition "Marquer un devis accepté (par le client)" — marks a quote as accepted by the client
Attacks that exploit this kind of access
Marquer un devis accepté (par le client). 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.
accept_quote accepts 1 parameter: quote_id. Required: quote_id. 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 accept_quote: 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.
accept_quote 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 accept_quote 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 accept_quote. 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.
accept_quote 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 →