export_transfers
A write tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/export-transfers.md
What export_transfers does on ServiceTitan MCP Server
AI agents use export_transfers 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_transfers is rated Medium
Without a description, classification relies on the tool name. 'export_transfers' most likely creates or writes exported data (Write category). It could potentially be Read if it only retrieves transfers, but 'export' suggests data is being written to a new location/format.
From the tool's definition Tool name 'export_transfers' indicates data export/write operation. Description is empty, limiting certainty. Context from sibling tools (adjustments_update, adjustments_get_list) suggests this server handles business data modification.
Attacks that exploit this kind of access
The rule that runs export_transfers 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_transfers, this is the rule to start with:
export_transfers 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_transfers call is checked against it from then on.
Questions about export_transfers
export_transfers 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_transfers: 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_transfers 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_transfers 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_transfers. 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_transfers 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