create_ticket · Eyeot MCP: Risk & Policy

WHAT IT DOES

What create_ticket does on Eyeot

AI agents use create_ticket 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_ticket needs a policy

This tool creates a new IT ticket in the eyeot ERP system. Creating a ticket is a reversible Write operation—it modifies system state by adding a new record but does not execute arbitrary code, delete data irreversibly, or move money.

From the tool's definition Tool name is 'create_ticket' and description states 'Créer un ticket IT' (Create an IT ticket). The verb 'create' indicates data creation; tickets are typically reversible records that can be deleted or updated.

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

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_ticket Rate-limited

create_ticket 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_ticket": {
      "limits": [
        {
          "counter": "create_ticket_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_ticket

What does the create_ticket tool do? +

Créer un ticket IT. 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_ticket accept? +

create_ticket 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_ticket? +

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

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

Can I rate-limit create_ticket? +

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

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

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