List currently open (non-closed) ConnectWise tickets.
AI agents call get_open_tickets 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 queries and returns data about existing tickets without creating, modifying, or deleting any records. The verb 'List' and 'get' prefix are characteristic of Read operations. Exposure of this tool carries minimal risk as it only surfaces information already accessible within the system, though the information returned could be sensitive depending on ticket contents.
From the tool's definition Tool name 'get_open_tickets' and description 'List currently open (non-closed) ConnectWise tickets' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List currently open (non-closed) ConnectWise tickets. 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_open_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 ConnectWise Live MCP Server. Nothing to install.
get_open_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 get_open_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 get_open_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.
get_open_tickets 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 →