arrival_windows_update
A write tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/arrival-windows-update.md
What arrival_windows_update does on ServiceTitan MCP Server
AI agents use arrival_windows_update 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 arrival_windows_update is rated Medium
The 'update' verb indicates this tool modifies existing data (arrival windows, likely service appointment scheduling). This is reversible data modification without permanent deletion, fitting the Write category. Severity is high because modifying arrival windows in a service business context could impact scheduling, customer communication, and business operations.
From the tool's definition Tool name 'arrival_windows_update' contains 'update', indicating data modification. Description is empty, preventing direct confirmation of specific effects.
Attacks that exploit this kind of access
The rule that runs arrival_windows_update 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 arrival_windows_update, this is the rule to start with:
arrival_windows_update 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 arrival_windows_update call is checked against it from then on.
Questions about arrival_windows_update
arrival_windows_update 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 arrival_windows_update: 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.
arrival_windows_update 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 arrival_windows_update 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 arrival_windows_update. 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.
arrival_windows_update 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