AI agents call list_tickets to retrieve information from Pearlog without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
term | string | — | Search term to filter tickets by headline/description. |
type | string | — | Filter by ticket type. |
limit | number | — | Maximum number of tickets to return. Defaults to 100. |
status | number | — | Filter by status ID. Use get_status_labels to see available statuses. |
userId | number | — | Filter by assigned user ID. |
projectId | number | — | Filter by project ID. |
Parameters from the server's own tool schema.
This tool performs a read-only operation that retrieves or lists existing tickets based on filter criteria. It does not create, modify, delete, or execute any actions—it only queries and returns data. This is a classic Read category operation with minimal risk if misused by an AI agent, as the worst outcome would be unauthorized information disclosure rather than data corruption or system compromise.
From the tool's definition Tool name 'list_tickets' and description 'List tickets with optional filters. Use this to browse tickets by project, assignee, status, or type.' indicate retrieval and querying of data with no side effects.
Attacks that exploit this kind of access
List tickets with optional filters. Use this to browse tickets by project, assignee, status, or type. It is categorised as a Read tool in the Pearlog MCP Server, which means it retrieves data without modifying state.
list_tickets accepts 6 parameters: term, type, limit, status, userId, projectId. The full parameter table on this page comes from the server's own tool schema.
Register the Pearlog 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 Pearlog. 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 Pearlog MCP server (mcp-server-pearlog). 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 →