jobs_complete
A execute tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/jobs-complete.md
What jobs_complete does on ServiceTitan MCP Server
AI agents invoke jobs_complete to trigger actions in ServiceTitan MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why jobs_complete is rated High
The tool name implies marking a job as complete, which is an external operation that triggers a state transition in ServiceTitan (likely irreversible or difficult to undo). With no description available, confidence is low, but 'complete' actions in field service management typically finalize billing, dispatch, and records.
From the tool's definition Tool name 'jobs_complete' suggests completing/finalizing a job in ServiceTitan; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs jobs_complete 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 jobs_complete, this is the rule to start with:
jobs_complete stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 jobs_complete call is checked against it from then on.
Questions about jobs_complete
jobs_complete is a execute tool on the ServiceTitan MCP Server MCP server. It is categorised as a Execute tool in the ServiceTitan MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ServiceTitan MCP Server MCP server in PolicyLayer and add a rule for jobs_complete: 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.
jobs_complete is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the jobs_complete 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 jobs_complete. 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.
jobs_complete 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