contact_methods_DeleteContactMethod
A destructive tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/contact-methods-deletecontactmethod.md
What contact_methods_DeleteContactMethod does on ServiceTitan MCP Server
AI agents call contact_methods_DeleteContactMethod 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 contact_methods_DeleteContactMethod is rated Critical
The tool name explicitly indicates a DELETE operation on contact method records. Even though the description is empty, the 'Delete' verb combined with the context of a CRM/business management API (ServiceTitan) strongly suggests this performs an irreversible removal of data. This is classified as Destructive rather than Write because deletion cannot be undone without external recovery mechanisms.
From the tool's definition Tool name contains 'Delete' and 'ContactMethod'; it appears to irreversibly remove contact method data based on the naming convention and its sibling tools which include read, write, and update operations.
Attacks that exploit this kind of access
The rule that runs contact_methods_DeleteContactMethod 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 contact_methods_DeleteContactMethod, this is the rule to start with:
contact_methods_DeleteContactMethod 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 contact_methods_DeleteContactMethod call is checked against it from then on.
Questions about contact_methods_DeleteContactMethod
contact_methods_DeleteContactMethod 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 contact_methods_DeleteContactMethod: 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.
contact_methods_DeleteContactMethod 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 contact_methods_DeleteContactMethod 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 contact_methods_DeleteContactMethod. 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.
contact_methods_DeleteContactMethod 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