Get schedule entries for a specific ticket
AI agents call connectwise_get_ticket_schedules to retrieve information from ConnectWise 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 schedule information associated with tickets without creating, modifying, or deleting any data. It is a simple read operation on existing ConnectWise Manage data. The read-only nature of the server and the absence of any side effects place it firmly in the Read category with low severity.
From the tool's definition Tool name 'connectwise_get_ticket_schedules' and description 'Get schedule entries for a specific ticket' indicate data retrieval. Server description explicitly states 'read-only access'.
Attacks that exploit this kind of access
Get schedule entries for a specific ticket. It is categorised as a Read tool in the ConnectWise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ConnectWise MCP Server MCP server in PolicyLayer and add a rule for connectwise_get_ticket_schedules: 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 MCP Server. Nothing to install.
connectwise_get_ticket_schedules 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 connectwise_get_ticket_schedules 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 connectwise_get_ticket_schedules. 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.
connectwise_get_ticket_schedules is provided by the ConnectWise MCP Server MCP server (taddiemason/connectwise-mcp-server). 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 →