list_tickets

List support tickets on the TrekMail account. Supports filtering by status and category. Returns paginated results.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/list-tickets.md

WHAT IT DOES

What list_tickets does on TrekMail MCP Server

AI agents call list_tickets to retrieve information from TrekMail MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_tickets is rated Low

This tool retrieves and queries existing support ticket data from the TrekMail account with optional filtering. It has no side effects, does not modify or delete data, and does not execute external operations. It is a straightforward data retrieval function, fitting the Read category.

From the tool's definition Tool name is 'list_tickets' and description states it 'List support tickets' and 'Returns paginated results' — core query operation with no modification, deletion, or execution of commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_tickets safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_tickets, this is the rule to start with:

list_tickets Allowed

list_tickets is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_tickets": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every list_tickets call is checked against it from then on.

FAQ

Questions about list_tickets

What does the list_tickets tool do? +

List support tickets on the TrekMail account. Supports filtering by status and category. Returns paginated results. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_tickets? +

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

list_tickets is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_tickets? +

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

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

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

KEEP EXPLORING

More on TrekMail MCP Server, and thousands of servers like it.

This server

All 248 TrekMail MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →