get_time_entries
AI agents call get_time_entries 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.
Based on naming convention alone, 'get_time_entries' appears to retrieve time tracking data without modifying it. This is a read operation with low blast radius—querying time entries poses minimal risk even if misused by an AI agent. The empty description slightly lowers confidence, but the naming pattern is clear enough to categorize as Read.
From the tool's definition Tool name 'get_time_entries' indicates a retrieval operation. The description is empty, providing no additional context, but the 'get_' prefix is a standard pattern for read-only data fetching operations.
Attacks that exploit this kind of access
get_time_entries. 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_time_entries: 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_time_entries 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_time_entries 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_time_entries. 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_time_entries 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 →