# scheduler_scheduler_performance

A execute tool on the ServiceTitan MCP Server MCP server.

Agent View of the PolicyLayer registry record for `scheduler_scheduler_performance`. HTML page: https://policylayer.com/tools/jordandalton-servicetitanmcpserver/scheduler-scheduler-performance

## Facts

- Tool: `scheduler_scheduler_performance`
- Server: ServiceTitan MCP Server (`jordandalton/servicetitanmcpserver`) — https://policylayer.com/tools/jordandalton-servicetitanmcpserver.md
- Homepage: https://github.com/JordanDalton/ServiceTitanMcpServer
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "scheduler_scheduler_performance",
    "arguments": {}
  }
}
```

## Why scheduler_scheduler_performance is rated High

scheduler_scheduler_performance triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

## Use case

AI agents invoke scheduler_scheduler_performance to trigger actions in ServiceTitan MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches ServiceTitan MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "scheduler_scheduler_performance": {
      "limits": [
        {
          "counter": "scheduler_scheduler_performance_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on ServiceTitan MCP Server (453)

- `appointments_delete` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/appointments-delete.md
- `appointments_remove_hold` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/appointments-remove-hold.md
- `bulk_tags_remove_tags` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/bulk-tags-remove-tags.md
- `categories_delete` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/categories-delete.md
- `contact_methods_DeleteContactMethod` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/contact-methods-deletecontactmethod.md
- `contacts_deletecontact` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/contacts-deletecontact.md
- `contacts_deletecontactrelationship` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/contacts-deletecontactrelationship.md
- `customers_delete_contact` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/customers-delete-contact.md
- `customers_delete_note` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/customers-delete-note.md
- `customers_delete_tag` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/customers-delete-tag.md
- `DiscountAndFees_Delete` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/discountandfees-delete.md
- `equipment_delete` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/equipment-delete.md
- `estimates_delete_item` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/estimates-delete-item.md
- `gross_pay_items_delete` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/gross-pay-items-delete.md
- `invoices_delete_invoice_item` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/invoices-delete-invoice-item.md
- `jobs_cancel` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/jobs-cancel.md
- `jobs_remove_cancellation` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/jobs-remove-cancellation.md
- `locations_delete_contact` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/locations-delete-contact.md
- `locations_delete_note` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/locations-delete-note.md
- `locations_delete_tag` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/locations-delete-tag.md
- `materials_delete` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/materials-delete.md
- `non_job_appointments_delete` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/non-job-appointments-delete.md
- `purchase_orders_cancel` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/purchase-orders-cancel.md
- `purchase_orders_markup_delete` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/purchase-orders-markup-delete.md
- `receipts_cancelreceipts` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/receipts-cancelreceipts.md
- `returns_cancel` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/returns-cancel.md
- `services_delete` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/services-delete.md
- `suppressions_remove` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/suppressions-remove.md
- `team_delete` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/team-delete.md
- `technician_shifts_bulk_delete` — Destructive — https://policylayer.com/tools/jordandalton-servicetitanmcpserver/technician-shifts-bulk-delete.md
- …and 423 more: https://policylayer.com/tools/jordandalton-servicetitanmcpserver.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=jordandalton-servicetitanmcpserver · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/jordandalton-servicetitanmcpserver