SECOPS
Cloudflare bot surge: propose rate-limit rules for review
Watches Cloudflare analytics for an abnormal spike in bot-scored requests, drafts a targeted rate-limit rule for the affected path or ASN.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 5 min: pull Cloudflare zone analyticsCloudflare
- LogicBot-traffic rate exceeds rolling baseline?
- ActionIdentify top path, ASN, and user-agentCloudflare
- LogicDraft scoped rate-limit rule (not yet live)
- OutputPost rule + evidence to Slack for approvalSlack
What it does
Detects a sudden surge in bot-classified traffic on a Cloudflare zone, identifies the hottest path and source signature, and proposes a precise rate-limit rule. Nothing is enforced automatically — the proposed rule is posted to Slack so an on-call operator can approve, edit, or reject it.
When to use it
Run this on any production zone that gets scraped or hit by credential-stuffing waves. It catches early surges before they degrade origin performance, while keeping a human in the loop so legitimate traffic spikes (a launch, a campaign) aren't throttled by mistake.
How it works
- 1A schedule fires every few minutes and pulls recent request analytics from Cloudflare via GraphQL.
- 2A logic step compares the current bot-score-weighted request rate against a rolling baseline; if it exceeds the surge threshold the flow continues, otherwise it exits.
- 3An action queries Cloudflare for the top path, ASN, and user-agent driving the spike.
- 4A logic step composes a scoped rate-limit rule (path + threshold + action: managed challenge) as a draft, not a live change.
- 5The proposal, with traffic evidence, is posted to a Slack approval channel with Approve / Reject buttons that gate the actual Cloudflare ruleset write.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More SecOps workflows
Post-Revocation Verification and Audit Logging
After a key is revoked, it confirms the old credential actually fails, verifies the replacement works.
Page on-call when a WAF rule mass-blocks legitimate traffic
On demand or every few minutes, it detects a single Cloudflare WAF rule suddenly blocking a broad spread of ASNs and paths (a likely false-positive storm).
PII Content Scan on New Dropbox External Share
When a file gets an external Dropbox link, it reads the file content, uses an AI classifier to detect PII or secrets.
Compile a weekly WAF tuning review with trends to Confluence
Every week an agent rolls up Cloudflare WAF block clusters by rule and ASN, compares them to prior weeks for trend direction.
Sensitive Dropbox Link Owner Remediation Loop
When a newly created Dropbox shared link points to a sensitive file, this workflow DMs the file owner, gives them a deadline to justify or revoke it.
GitLab Push Secret Detection to Block and History Purge
On a GitLab push that contains a detected secret, it revokes the exposed credential, opens a tracking issue with git-history purge instructions.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.