services_get

What services_get does on ServiceTitan MCP Server

AI agents call services_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 services_get is rated Low

The 'get' suffix in the tool name and consistency with sibling tools that use 'get' for queries and 'update' for modifications strongly indicates this retrieves service data without side effects. Low severity because read-only operations have minimal blast radius unless the data itself is highly sensitive (business configuration details), which is typical for service management APIs but not inherently critical.

From the tool's definition Tool name 'services_get' follows the RESTful GET convention indicating a retrieval operation. Context from sibling tools (all *_get, *_get_list patterns) shows this server's naming convention uses 'get' exclusively for read operations and 'update' for writes.

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

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

Questions about services_get