List tickets with optional filters by status and priority. Returns up to 50 tickets with AI summary.
AI agents call list_tickets to retrieve information from Vidal Helpdesk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries existing ticket data with optional filtering parameters. It has no side effects, creates no data, executes no commands, and does not destructively modify or delete records. This is a straightforward read-only data retrieval function, typical of helpdesk query operations. Severity is low because querying ticket metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'list_tickets' and description explicitly states it 'List tickets with optional filters by status and priority. Returns up to 50 tickets with AI summary.' This is a retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
List tickets with optional filters by status and priority. Returns up to 50 tickets with AI summary. It is categorised as a Read tool in the Vidal Helpdesk MCP Server, which means it retrieves data without modifying state.
Register the Vidal Helpdesk 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 Vidal Helpdesk. Nothing to install.
list_tickets 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 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.
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.
list_tickets is provided by the Vidal Helpdesk MCP server (vidal-renao/vidal-helpdesk-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 →