AI agents call get_client to retrieve information from Eyeot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
client_id | string | Yes | (path parameter) |
Parameters from the server's own tool schema.
This tool fetches data about a single client entity identified by an ID. It performs no modifications, deletions, or external operations. While the ERP context means client data may be sensitive (e.g., contact info, financial details), the read-only nature classifies it as Read category.
From the tool's definition Tool name is 'get_client' and description states 'Récupérer un client par id' (Retrieve a client by id). The verb 'Retrieve' and the singular lookup pattern indicate a read-only query operation with no side effects.
Attacks that exploit this kind of access
Récupérer un client par id. It is categorised as a Read tool in the Eyeot MCP Server, which means it retrieves data without modifying state.
get_client accepts 1 parameter: client_id. Required: client_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 get_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.
get_client is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
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 →