calls_update · ServiceTitan MCP Server MCP: Risk & Policy

WHAT IT DOES

What calls_update does on ServiceTitan MCP Server

AI agents use calls_update to create or update resources in ServiceTitan MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ServiceTitan MCP Server environment.

WHY IT NEEDS A POLICY

Why calls_update needs a policy

An AI agent can call calls_update faster than any human can review — one bad instruction and it creates or modifies resources in ServiceTitan MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

calls_update Rate-limited

calls_update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "calls_update": {
      "limits": [
        {
          "counter": "calls_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ServiceTitan MCP Server, so you can run agents against it safely.

FAQ

Questions about calls_update

What does the calls_update tool do? +

calls_update. It is categorised as a Write tool in the ServiceTitan MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on calls_update? +

Register the ServiceTitan MCP Server MCP server in PolicyLayer and add a rule for calls_update: 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 calls_update? +

calls_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit calls_update? +

Yes. Add a rate_limit block to the calls_update 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 calls_update completely? +

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

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