payments_get_custom_field_types

What payments_get_custom_field_types does on ServiceTitan MCP Server

AI agents call payments_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 payments_get_custom_field_types is rated Low

The tool appears to retrieve metadata about custom field types associated with payments, likely returning configuration or schema information. The 'get' verb indicates a read-only operation with no side effects. While it operates in the payments domain (which could be financial context), the operation itself is merely querying field type definitions, not moving money or creating financial obligations.

From the tool's definition Tool name 'payments_get_custom_field_types' contains 'get' which indicates data retrieval. The naming pattern matches sibling tools like 'activities_controllers_get', 'activity_categories_get', and 'adjustments_get_list' which are read operations.

The rule that runs payments_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 payments_get_custom_field_types, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "payments_get_custom_field_types": {}
  }
}

Questions about payments_get_custom_field_types