create_ticket · TrekMail MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_ticket does on TrekMail MCP Server

AI agents use create_ticket to create or update resources in TrekMail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TrekMail MCP Server environment.

WHY IT NEEDS A POLICY

Why create_ticket needs a policy

Creating a support ticket is a write operation that generates new data in a ticketing system. It has no irreversible consequences, does not execute arbitrary code, and does not involve financial transactions. The blast radius is minimal—a mistaken ticket can be easily closed or deleted by an administrator. Low severity reflects the reversible and low-impact nature of ticket creation.

From the tool's definition Tool name 'create_ticket' and description 'Create a new support ticket' indicate creation of a new record with reversible effects (tickets can be modified, reassigned, or closed).

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 TrekMail MCP Server, so you can run agents against it safely.

FAQ

Questions about create_ticket

What does the create_ticket tool do? +

Create a new support ticket. Requires a subject, category, and initial message. It is categorised as a Write tool in the TrekMail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_ticket? +

Register the TrekMail MCP Server 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 TrekMail MCP Server. 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 TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.