SLA Breach Watchdog

Name: SLA Breach Watchdog
Availability: InStock
Author: Kata Team

Catches SLA breaches before they happen, and alerts once per ticket instead of every fifteen minutes.

Requires external credentials

After connecting, this agent asks for your own API keys for third-party services to work. Only provide keys you trust this agent with — review its setup before connecting any account.

Works with

Claude (web & desktop)ChatGPT (Plus / Pro)CursorVS Code (Copilot)Claude CodeGemini CLIWindsurfClineContinueZedLM StudioGooseJetBrains AI AssistantWarpPostmanand more

Before you connect: what this agent would do

A preview derived from this agent’s definition — not a live run. Nothing runs and no key is sent until you connect. FindAgent runs it on the hosted connection.

Tools it can use (6)

list_sla_policiesRead-only
List the configured Zendesk SLA policies with their targets and the ticket conditions each applies to.
Reaches: {subdomain}.zendesk.com
Uses your Zendesk API credential.
search_open_ticketsRead-only
Find unsolved tickets in a group that have not already been alerted on, newest first.
Reaches: {subdomain}.zendesk.com
Uses your Zendesk API credential.
get_ticket_metricsRead-only
Fetch a ticket's SLA metrics, including reply and resolution times in both business and calendar minutes.
Reaches: {subdomain}.zendesk.com
Uses your Zendesk API credential.
post_sla_alertCan change data
Post one consolidated alert to the support channel listing every at-risk and breached ticket found this run.
Reaches: slack.com
Uses your Slack bot token.
trigger_pagerduty_incidentCan change data
Open a PagerDuty incident for a single urgent ticket that has breached or is minutes from breaching.
Reaches: api.pagerduty.com
Uses your PagerDuty REST API key.
mark_ticket_alertedCan change data
Record on the ticket that an alert was raised, and tag it so the next run does not alert on it again.
Reaches: {subdomain}.zendesk.com
Uses your Zendesk API credential.

Credentials it will ask for (3)

Zendesk API credential
Only ever sent to: zendesk.com
Format: Paste the Base64 encoding of “id:token” (e.g. your email and API token joined by a colon), not the raw token. Many tools show this ready-made as your “Basic auth” value.
Slack bot token
Only ever sent to: slack.com
PagerDuty REST API key· optional
Only ever sent to: api.pagerduty.com
Format: Enter the full authorization value, including any scheme word (e.g. “token ghp_…”).

Safety rails that guard it

Every result is scanned for leaked secrets and prompt-injection before it reaches you — a check no agent can turn off.
These personal details are removed from your input before the agent sees them: Credit card, IBAN, National ID.
These personal details are stripped from the agent’s results before you see them: Email, Phone.
A request larger than 80,000 characters is rejected before it runs.
post_sla_alertRate limited to 12/hour.Runs only after list_sla_policies has run first.
list_sla_policiesRate limited to 60/hour.Safe to retry automatically if a run is interrupted.
get_ticket_metricsRate limited to 1200/hour.Safe to retry automatically if a run is interrupted.
mark_ticket_alertedRate limited to 300/hour.Safe to retry automatically if a run is interrupted.
search_open_ticketsRate limited to 240/hour.Safe to retry automatically if a run is interrupted.
trigger_pagerduty_incidentRate limited to 6/hour.Runs only after list_sla_policies has run first.

How FindAgent keeps agents safe

Run locally

This MCP server runs on your own machine — FindAgent only points you at it. Run the command below, then add it to your MCP client. Nothing is hosted or proxied on our side.

terminal

npx -y @findagent/mcp run

Add it to your MCP client

Paste this into your client config (e.g. claude_desktop_config.json or a Cursor mcp.json), then restart the client.

mcp client config

{
  "mcpServers": {
    "sla-breach-watchdog": {
      "command": "npx",
      "args": [
        "-y",
        "@findagent/mcp",
        "run"
      ]
    }
  }
}

What you'll need — and where to get it

This agent will ask you for the following. You enter them when you connect — they're encrypted and never shared with the creator.

Zendesk API credential
Base64 of 'your-agent-email/token:YOUR_API_TOKEN' — encode it yourself before pasting; the runtime only adds the Basic prefix. Create the token under Admin Center > Apps and integrations > Zendesk API.
Get this from zendesk.com's account or API settings.
Paste the value as a single line.
Only sent to: zendesk.com
Slack bot token
A bot token starting with xoxb-. Needs chat:write, and the bot must be invited to the alert channel.
Create a Slack app (api.slack.com/apps), add the scopes the agent needs, install it to your workspace, and copy the bot/user token.
Paste the value as a single line.
Only sent to: slack.com
PagerDuty REST API key · optional
The complete Authorization value including its prefix: Token token=YOUR_REST_API_KEY. Use a PagerDuty REST API key, not an Events API routing key. Optional — without it the agent still posts Slack alerts and simply never pages.
Get this from pagerduty.com's account or API settings.
Paste the value as a single line.
Only sent to: api.pagerduty.com

Requirements

This server requires authentication — see the description for how to get a key.

Kata Team

Free

SLA Breach Watchdog

Before you connect: what this agent would do

Tools it can use (6)

Credentials it will ask for (3)

Safety rails that guard it

Run locally

Add it to your MCP client

What you'll need — and where to get it

Requirements

Related agents

Tier-1 Ticket Deflection Agent

Stalled Deal Detective

Support Ticket Router

Refund & Credit Advisor

Support Content Generator

Support Shift Handover

More from @team886

Jira Reporting Agent

Aso Skills

AI Visibility Tracker