export_location_recurring_service_events
A read tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/export-location-recurring-service-events.md
What export_location_recurring_service_events does on ServiceTitan MCP Server
AI agents call export_location_recurring_service_events to retrieve information from ServiceTitan MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why export_location_recurring_service_events is rated Low
The tool name suggests exporting (reading/retrieving) recurring service event data from ServiceTitan. Export operations are typically read-only data extractions. However, the empty description lowers confidence. Severity is medium because exported data could contain sensitive business information about service schedules and customer locations.
From the tool's definition Tool name contains 'export' and 'recurring_service_events', suggesting data retrieval/export; description is empty providing no additional context.
Attacks that exploit this kind of access
The rule that runs export_location_recurring_service_events 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_service_events, this is the rule to start with:
export_location_recurring_service_events is read-only, so it stays allowed. 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_service_events call is checked against it from then on.
Questions about export_location_recurring_service_events
export_location_recurring_service_events is a read tool on the ServiceTitan MCP Server MCP server. It is categorised as a Read tool in the ServiceTitan MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ServiceTitan MCP Server MCP server in PolicyLayer and add a rule for export_location_recurring_service_events: 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_service_events is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the export_location_recurring_service_events 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_service_events. 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_service_events 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