project_substatuses_get
A read tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/project-substatuses-get.md
What project_substatuses_get does on ServiceTitan MCP Server
AI agents call project_substatuses_get 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 project_substatuses_get is rated Low
The tool follows a standard naming convention for retrieval operations ('_get' suffix). No modifying, destructive, or financial keywords are present. The tool appears to retrieve project substatus data from ServiceTitan API without side effects, consistent with other sibling GET operations on this server.
From the tool's definition Tool name 'project_substatuses_get' contains the verb 'get', which indicates data retrieval. The naming pattern is consistent with sibling tools like 'activities_controllers_get', 'activity_categories_get', and 'activity_codes_get', all of which are read…
Attacks that exploit this kind of access
The rule that runs project_substatuses_get 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 project_substatuses_get, this is the rule to start with:
project_substatuses_get 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 project_substatuses_get call is checked against it from then on.
Questions about project_substatuses_get
project_substatuses_get 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 project_substatuses_get: 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.
project_substatuses_get 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 project_substatuses_get 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 project_substatuses_get. 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.
project_substatuses_get 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