locations_delete_tag
A destructive tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/locations-delete-tag.md
What locations_delete_tag does on ServiceTitan MCP Server
AI agents call locations_delete_tag 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 locations_delete_tag is rated Critical
The 'delete' action in the tool name indicates this operation removes data irreversibly. Even though the description is empty, the name clearly signals a destructive action. In a ServiceTitan context (field service management platform), deleting location tags could have significant business impact if done incorrectly—tags often organize critical data like service areas, customer segments, or operational categories.
From the tool's definition Tool name is 'locations_delete_tag' with 'delete' action verb. Description is empty, limiting direct evidence, but the 'delete' operation indicates irreversible removal of a tag associated with locations.
Attacks that exploit this kind of access
The rule that runs locations_delete_tag 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 locations_delete_tag, this is the rule to start with:
locations_delete_tag 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 locations_delete_tag call is checked against it from then on.
Questions about locations_delete_tag
locations_delete_tag 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 locations_delete_tag: 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.
locations_delete_tag 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 locations_delete_tag 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 locations_delete_tag. 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.
locations_delete_tag 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