List tickets with optional filtering by status, assignee, or system
AI agents call list_tickets to retrieve information from MCP FOR ITSM without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries ticket data with optional filters (status, assignee, system). It performs no creation, modification, deletion, or execution of external operations. It is a straightforward read operation with minimal security risk—exposure allows an AI agent to view tickets but not alter them or trigger actions. Confidence is high due to clear intent from both name and description.
From the tool's definition Tool name 'list_tickets' and description 'List tickets with optional filtering by status, assignee, or system' indicate a query operation that retrieves ticket data without modification or side effects.
Attacks that exploit this kind of access
List tickets with optional filtering by status, assignee, or system. It is categorised as a Read tool in the MCP FOR ITSM MCP Server, which means it retrieves data without modifying state.
Register the MCP FOR ITSM 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 MCP FOR ITSM. 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 MCP FOR ITSM MCP server (madosh/mcp-itsm). 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 →