attributed_leads_get
A read tool on the ServiceTitan MCP server.
This record as markdown: /tools/jordandalton-servicetitanmcpserver/attributed-leads-get.md
What attributed_leads_get does on ServiceTitan MCP Server
AI agents call attributed_leads_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 attributed_leads_get is rated Low
The '_get' suffix and parallel structure with other retrieval-only tools on the server indicate this is a query/fetch operation that retrieves lead data. No description of parameters or return values limits confidence slightly, but the naming pattern is conclusive. This poses low risk as it only reads data without modification, deletion, or execution of external operations.
From the tool's definition Tool name 'attributed_leads_get' follows naming convention of sibling tools (e.g., 'activities_controllers_get', 'activity_codes_get') that consistently use '_get' suffix indicating retrieval operations.
Attacks that exploit this kind of access
The rule that runs attributed_leads_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 attributed_leads_get, this is the rule to start with:
attributed_leads_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 attributed_leads_get call is checked against it from then on.
Questions about attributed_leads_get
attributed_leads_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 attributed_leads_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.
attributed_leads_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 attributed_leads_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 attributed_leads_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.
attributed_leads_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