Get a count of tickets matching the given filters (faster than fetching full list).
AI agents call get_ticket_count to retrieve information from ConnectWise Live MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves summary statistics about tickets based on filter criteria. It has no side effects, creates no data, executes no commands, and causes no destructive changes. It is a straightforward read operation with minimal security risk even if misused by an AI agent, as the worst outcome is retrieving a count of existing tickets within filter scope.
From the tool's definition Tool description states 'Get a count of tickets matching the given filters' — a retrieval operation that returns aggregated data without modifying anything. The comparative note 'faster than fetching full list' confirms it performs a query-like operation.
Attacks that exploit this kind of access
Get a count of tickets matching the given filters (faster than fetching full list). It is categorised as a Read tool in the ConnectWise Live MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ConnectWise Live MCP Server MCP server in PolicyLayer and add a rule for get_ticket_count: 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 ConnectWise Live MCP Server. Nothing to install.
get_ticket_count 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_count 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_count. 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_count is provided by the ConnectWise Live MCP Server MCP server (mfrostbutter/connectwise-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 →