export_location_recurring_services
A write tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/export-location-recurring-services.md
What export_location_recurring_services does on ServiceTitan MCP Server
AI agents use export_location_recurring_services to create or update resources in ServiceTitan MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceTitan MCP Server environment.
Why export_location_recurring_services is rated Medium
The tool likely exports or modifies recurring service data associated with locations. In ServiceTitan (a field service software), recurring services are tied to billing/revenue cycles. While 'export' could imply read-only data retrieval, the context (recurring_services, standing alongside adjustment_update) suggests it may persist export state or modify service subscriptions.
From the tool's definition Tool name contains 'export_location_recurring_services'; sibling tools show patterns of read operations (get, get_list) and write operations (adjustments_update).
Attacks that exploit this kind of access
The rule that runs export_location_recurring_services 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 export_location_recurring_services, this is the rule to start with:
export_location_recurring_services stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ServiceTitan MCP Server, apply this rule, and every export_location_recurring_services call is checked against it from then on.
Questions about export_location_recurring_services
export_location_recurring_services is a write tool on the ServiceTitan MCP Server MCP server. It is categorised as a Write tool in the ServiceTitan MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ServiceTitan MCP Server MCP server in PolicyLayer and add a rule for export_location_recurring_services: 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.
export_location_recurring_services is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export_location_recurring_services 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 export_location_recurring_services. 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.
export_location_recurring_services 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.
This server
Across the catalogue