customers_get_custom_field_types
A read tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/customers-get-custom-field-types.md
What customers_get_custom_field_types does on ServiceTitan MCP Server
AI agents call customers_get_custom_field_types 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 customers_get_custom_field_types is rated Low
The 'get' verb in the tool name indicates a read operation that retrieves custom field type definitions for customers. This is a non-destructive query operation. Confidence is moderate (0.7) rather than high because the description is empty, leaving some ambiguity about exact functionality, but the naming pattern strongly aligns with read operations evident in the sibling tool set.
From the tool's definition Tool name 'customers_get_custom_field_types' contains 'get', indicating data retrieval. Description is empty, but the naming convention and context of sibling tools (all read/list operations like 'activities_controllers_get', 'activity_categories_get')…
Attacks that exploit this kind of access
The rule that runs customers_get_custom_field_types 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 customers_get_custom_field_types, this is the rule to start with:
customers_get_custom_field_types 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 customers_get_custom_field_types call is checked against it from then on.
Questions about customers_get_custom_field_types
customers_get_custom_field_types 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 customers_get_custom_field_types: 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.
customers_get_custom_field_types 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 customers_get_custom_field_types 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 customers_get_custom_field_types. 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.
customers_get_custom_field_types 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