New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

call_reasons_get

A read tool on the ServiceTitan MCP server.

SERVERServiceTitan MCP Server SOURCEjordandalton/servicetitanmcpserver
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jordandalton-servicetitanmcpserver/call-reasons-get.md

What call_reasons_get does on ServiceTitan MCP Server

AI agents call call_reasons_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 call_reasons_get is rated Low

The tool name uses the '_get' suffix which consistently indicates read operations across the ServiceTitan MCP server's tool suite. There is no evidence of modification, deletion, execution, or financial impact. The lack of a description slightly reduces confidence, but the naming pattern is clear and consistent with other confirmed read operations on the same server.

From the tool's definition Tool name 'call_reasons_get' follows the naming pattern of sibling tools like 'activities_controllers_get', 'activity_codes_get', and 'activity_types_get', all of which are retrieval/query operations indicated by the '_get' suffix.

Questions about call_reasons_get

What does the call_reasons_get tool do? +

call_reasons_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.

How do I enforce a policy on call_reasons_get? +

Register the ServiceTitan MCP Server MCP server in PolicyLayer and add a rule for call_reasons_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.

What risk level is call_reasons_get? +

call_reasons_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit call_reasons_get? +

Yes. Add a rate_limit block to the call_reasons_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.

How do I block call_reasons_get completely? +

Set action: deny in the PolicyLayer policy for call_reasons_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.

What MCP server provides call_reasons_get? +

call_reasons_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ServiceTitan MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.