installed_equipment_create
A write tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/installed-equipment-create.md
What installed_equipment_create does on ServiceTitan MCP Server
AI agents use installed_equipment_create 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 installed_equipment_create is rated Medium
This tool creates new equipment records in ServiceTitan, which is a reversible write operation. The empty description limits confidence somewhat, but the naming convention is unambiguous. Severity is medium because creating erroneous equipment records in a service management system could cause operational issues (incorrect job assignments, billing problems) but these are typically correctable.
From the tool's definition Tool name 'installed_equipment_create' clearly indicates a creation/write operation. The '_create' suffix is a standard convention for tools that add new records.
Attacks that exploit this kind of access
The rule that runs installed_equipment_create 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 installed_equipment_create, this is the rule to start with:
installed_equipment_create 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 installed_equipment_create call is checked against it from then on.
Questions about installed_equipment_create
installed_equipment_create 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 installed_equipment_create: 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.
installed_equipment_create 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 installed_equipment_create 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 installed_equipment_create. 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.
installed_equipment_create 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