create_ticket
AI agents use create_ticket to create or update resources in ConnectWise Live MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ConnectWise Live MCP Server environment.
The tool creates new tickets, which are reversible modifications to the ConnectWise system. This is a Write operation—it generates new records but does not delete or irreversibly alter data. Severity is medium because unchecked ticket creation could flood the system with noise or create false work items, but the impact is contained and reversible.
From the tool's definition Tool name 'create_ticket' directly indicates creation of a ticket/work item in ConnectWise Manage. The 'create_' prefix and context among sibling tools (create_agreement, create_opportunity, create_project) confirm this is a data creation operation.
Attacks that exploit this kind of access
create_ticket. It is categorised as a Write tool in the ConnectWise Live MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ConnectWise Live MCP Server MCP server in PolicyLayer and add a rule for create_ticket: 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.
create_ticket is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_ticket 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 create_ticket. 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.
create_ticket 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 →