list_tickets
List support tickets with optional filters.
This record as markdown: /tools/io-favcrm-favcrm/list-tickets.md
What list_tickets does on FavCRM
AI agents call list_tickets to retrieve information from FavCRM without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max results (default 20) |
search | string | — | Search by subject |
status | string | — | Filter by status |
category | string | — | Filter by category |
priority | string | — | Filter by priority |
accountId | string | — | Filter by CRM account ID |
Parameters from the server's own tool schema.
Why list_tickets is rated Low
This tool retrieves and displays support tickets based on filter criteria. It performs a read-only operation that does not create, modify, delete, or execute any actions. The 'list' verb and 'filters' (for querying) are classic indicators of a Read category tool. There is no evidence of destructive capability, financial impact, or code execution.
From the tool's definition Tool name is 'list_tickets' and description states 'List support tickets with optional filters' — this is a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_tickets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every list_tickets call is checked against it from then on.
Questions about list_tickets
List support tickets with optional filters. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_tickets accepts 6 parameters: limit, search, status, category, priority, accountId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM 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 FavCRM. 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 FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue