client_side_data_get
A read tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/client-side-data-get.md
What client_side_data_get does on ServiceTitan MCP Server
AI agents call client_side_data_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 client_side_data_get is rated Low
The naming convention '_get' across the ServiceTitan MCP server consistently maps to Read operations. Although the description is empty, the tool name strongly suggests data retrieval with no side effects. Confidence is moderate rather than high due to lack of explicit description detail, but the naming pattern is reliable evidence.
From the tool's definition Tool name 'client_side_data_get' indicates a retrieval operation. The '_get' suffix is consistent with sibling tools that are Read operations (e.g., activities_controllers_get, activity_categories_get, activity_codes_get).
Attacks that exploit this kind of access
The rule that runs client_side_data_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 client_side_data_get, this is the rule to start with:
client_side_data_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 client_side_data_get call is checked against it from then on.
Questions about client_side_data_get
client_side_data_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 client_side_data_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.
client_side_data_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 client_side_data_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 client_side_data_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.
client_side_data_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