This record as markdown: /tools/io-favcrm-favcrm/get-ticket-stats.md
What get_ticket_stats does on FavCRM
AI agents call get_ticket_stats 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.
Why get_ticket_stats is rated Low
This is a straightforward read operation that retrieves and reports statistical data about tickets organized by status. It performs no side effects, makes no modifications to data, and poses minimal risk if misused by an agent—the worst outcome would be unnecessary API calls or information disclosure of non-sensitive aggregate counts.
From the tool's definition Tool name 'get_ticket_stats' and description 'Get ticket counts grouped by status' indicate a retrieval operation that queries aggregated ticket data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs get_ticket_stats 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 get_ticket_stats, this is the rule to start with:
get_ticket_stats 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 get_ticket_stats call is checked against it from then on.
Questions about get_ticket_stats
Get ticket counts grouped by status. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
Register the FavCRM MCP server in PolicyLayer and add a rule for get_ticket_stats: 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.
get_ticket_stats 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 get_ticket_stats 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 get_ticket_stats. 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.
get_ticket_stats 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