update_client · Eyeot MCP: Risk & Policy

WHAT IT DOES

What update_client does on Eyeot

AI agents use update_client 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.

PARAMETERS

Parameter	Type	Required	Description
`body`	object	Yes	Request body
`client_id`	string	Yes	(path parameter)

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why update_client needs a policy

This tool modifies client records reversibly within an ERP system. While updates can have business impact (e.g., changing payment terms, contact details, company classification), they are not irreversible (data can be updated again), do not execute arbitrary code, and do not move money.

From the tool's definition Tool name 'update_client' and description 'Mettre à jour un client' (Update a client) indicate modification of existing client data. The French description confirms this is an update operation, not creation or deletion.

Risk signalsAccepts raw HTML/template content (body) · High parameter count (15 properties)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_client Rate-limited

update_client stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_client": {
      "limits": [
        {
          "counter": "update_client_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Eyeot, so you can run agents against it safely.

FAQ

Questions about update_client

What does the update_client tool do? +

Mettre à jour un 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.

What parameters does update_client accept? +

update_client accepts 2 parameters: body, client_id. Required: body, client_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_client? +

Register the Eyeot MCP server in PolicyLayer and add a rule for update_client: 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.

What risk level is update_client? +

update_client is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_client? +

Yes. Add a rate_limit block to the update_client 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.

How do I block update_client completely? +

Set action: deny in the PolicyLayer policy for update_client. 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.

What MCP server provides update_client? +

update_client 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.