technician_shifts_bulk_delete
A destructive tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/technician-shifts-bulk-delete.md
What technician_shifts_bulk_delete does on ServiceTitan MCP Server
AI agents call technician_shifts_bulk_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 technician_shifts_bulk_delete is rated Critical
The 'bulk_delete' operation irreversibly removes data and cannot be undone, fitting the Destructive category definition. The 'bulk' aspect amplifies the blast radius to potentially many technician shift records simultaneously. While the description is empty (lowering confidence slightly), the name alone provides sufficient semantic evidence.
From the tool's definition Tool name contains 'bulk_delete' which explicitly indicates deletion of multiple records. The '_delete' suffix combined with 'bulk' modifier indicates irreversible removal of data at scale.
Attacks that exploit this kind of access
The rule that runs technician_shifts_bulk_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 technician_shifts_bulk_delete, this is the rule to start with:
technician_shifts_bulk_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 technician_shifts_bulk_delete call is checked against it from then on.
Questions about technician_shifts_bulk_delete
technician_shifts_bulk_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 technician_shifts_bulk_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.
technician_shifts_bulk_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 technician_shifts_bulk_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 technician_shifts_bulk_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.
technician_shifts_bulk_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