AI AGENTS

On-Call WAF Runbook Agent with Linear Postmortem

When a WAF alert fires, an agent reads the matching runbook, executes the documented Cloudflare remediation (toggling or tightening WAF rules).

CategoryAI Agents
Enginepaperclip
Difficultyadvanced
Triggerwebhook
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWAF alert webhook receivedHTTP webhook
  • ActionFetch matching runbook from MCP knowledge serverCustom MCP server
  • LogicDecide: auto-remediate or escalate to human
  • ActionApply documented Cloudflare WAF rule changeCloudflareCloudflare
  • ActionOpen pre-filled Linear postmortem stubLinearLinear
  • OutputPost remediation summary to Slack on-call channelSlack

What it does

Turns an incoming WAF alert into a hands-on remediation. An agent looks up the runbook that matches the alert signature, performs the exact Cloudflare WAF rule change the runbook prescribes, and files a Linear postmortem stub seeded with what it saw and what it did.

When to use it

Use it when your team has documented runbooks for common edge-security incidents (credential-stuffing spikes, bad-bot floods, suspicious path probing) and wants first-response remediation to happen in minutes, not after someone wakes up. Best when remediations are well-bounded and reversible.

How it works

  1. 1A WAF alert webhook arrives with the rule ID, zone, and attack signature.
  2. 2The agent fetches the matching runbook from your internal MCP knowledge server.
  3. 3It decides whether the documented action applies or needs a human (logic branch on confidence and blast radius).
  4. 4If clear, it applies the Cloudflare WAF rule change (enable, tighten sensitivity, or block the offending pattern).
  5. 5It opens a Linear postmortem stub pre-filled with the alert, runbook used, and action taken.
  6. 6It posts a Slack summary to the on-call channel with the Linear link.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Connect Custom MCP serverConnect any MCP-compatible tool you own.
  5. 5
    Connect HTTP webhookTrigger any URL on agent actions.
  6. 6
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  7. 7
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  8. 8
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.