TechnicianShifts_Delete
A destructive tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/technicianshifts-delete.md
What TechnicianShifts_Delete does on ServiceTitan MCP Server
AI agents call TechnicianShifts_Delete to permanently remove resources in ServiceTitan MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why TechnicianShifts_Delete is rated Critical
Delete operations are irreversible and remove data that cannot be recovered without external intervention (backups, audit logs). In a business context like ServiceTitan (a field service management platform), deleting technician shifts could disrupt scheduling, payroll records, and operational continuity.
From the tool's definition Tool name 'TechnicianShifts_Delete' explicitly contains 'Delete', which is listed in the Destructive category definition as an irreversible action. The empty description prevents confirmation of exact semantics, but the naming convention is unambiguous.
Attacks that exploit this kind of access
The rule that runs TechnicianShifts_Delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ServiceTitan MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For TechnicianShifts_Delete, this is the rule to start with:
TechnicianShifts_Delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceTitan MCP Server, apply this rule, and every TechnicianShifts_Delete call is checked against it from then on.
Questions about TechnicianShifts_Delete
TechnicianShifts_Delete is a destructive tool on the ServiceTitan MCP Server MCP server. It is categorised as a Destructive tool in the ServiceTitan MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ServiceTitan MCP Server MCP server in PolicyLayer and add a rule for TechnicianShifts_Delete: 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 ServiceTitan MCP Server. Nothing to install.
TechnicianShifts_Delete 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 TechnicianShifts_Delete 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 TechnicianShifts_Delete. 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.
TechnicianShifts_Delete is provided by the ServiceTitan MCP Server MCP server (jordandalton/servicetitanmcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ServiceTitan MCP Server, and thousands of servers like it.
Across the catalogue