create_opportunity · Eyeot MCP: Risk & Policy

WHAT IT DOES

What create_opportunity does on Eyeot

AI agents use create_opportunity 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

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why create_opportunity needs a policy

This tool creates an opportunity record in the eyeot ERP's CRM module. While reversible (opportunities can typically be deleted or modified), the action is a persistent data creation that could impact sales pipelines, financial forecasting, and business operations if misused by an AI agent (e.g., creating fraudulent or spurious opportunities).

From the tool's definition Tool name 'create_opportunity' with description 'Créer une opportunité' (Create an opportunity) directly indicates creation of a new business entity in an ERP system.

Risk signalsAccepts raw HTML/template content (body)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_opportunity Rate-limited

create_opportunity 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": {
    "create_opportunity": {
      "limits": [
        {
          "counter": "create_opportunity_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 create_opportunity

What does the create_opportunity tool do? +

Créer une opportunité. 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 create_opportunity accept? +

create_opportunity accepts 1 parameter: body. Required: body. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_opportunity? +

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

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

Can I rate-limit create_opportunity? +

Yes. Add a rate_limit block to the create_opportunity 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 create_opportunity completely? +

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

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