Unassign a resource (technician) from a service call ticket
AI agents call autotask_delete_service_call_ticket_resource to permanently remove resources in Autotask MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although 'unassign' might seem like a simple state change, in an MSP billing and ticketing context, removing a technician assignment from a ticket is a destructive operation that changes historical records and cannot be automatically undone.
From the tool's definition Tool name contains 'delete' and description says 'Unassign a resource (technician) from a service call ticket'.
Attacks that exploit this kind of access
Unassign a resource (technician) from a service call ticket. It is categorised as a Destructive tool in the Autotask MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Autotask MCP Server MCP server in PolicyLayer and add a rule for autotask_delete_service_call_ticket_resource: 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 Autotask MCP Server. Nothing to install.
autotask_delete_service_call_ticket_resource is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the autotask_delete_service_call_ticket_resource 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 autotask_delete_service_call_ticket_resource. 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.
autotask_delete_service_call_ticket_resource is provided by the Autotask MCP Server MCP server (ticnine/autotask-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 →