Get all time entries logged against a ticket.
AI agents call get_ticket_time 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 time entry records associated with a ticket without altering, creating, or removing any data. It performs a straightforward query operation with no side effects, making it a Read category risk. The blast radius is minimal as it only exposes existing time tracking information without the ability to modify systems or trigger external actions.
From the tool's definition Tool name 'get_ticket_time' and description 'Get all time entries logged against a ticket' indicate data retrieval with the verb 'Get' and no modification or deletion of data.
Attacks that exploit this kind of access
Get all time entries logged against a ticket. 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_time: 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_time 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_time 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_time. 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_time 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 →