IT OPS

Agent-Driven Cloudflare Access Drift Investigator

A CEO-driven agent reconciles Cloudflare Access grants against the HR system over a custom MCP server, investigates each discrepancy with context.

CategoryIT Ops
Enginepaperclip
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled agent run (twice weekly)
  • ActionEnumerate Cloudflare Access apps and grantsCloudflareCloudflare
  • ActionQuery HR system of record via custom MCPCustom MCP server
  • LogicAgent reasons per grant; assigns keep/revoke/escalate
  • ActionPersist dispositions and evidence to PostgresPostgreSQLPostgres
  • OutputPost prioritized findings to Slack for approvalSlack

What it does

Uses an agent rather than a fixed pipeline to reason about access drift. It compares Cloudflare Access grants to the HR system of record exposed through your custom MCP server, then investigates each mismatch, distinguishing genuine orphans from contractors, service accounts, and recently-rehired staff before recommending keep, revoke, or escalate.

When to use it

Use this when naive set-diffing produces too many false positives and you want judgment applied: shared mailboxes, vendor identities, and edge cases that a deterministic rule mislabels. Best when access ownership data is messy.

How it works

  1. 1A scheduled run kicks off the agent.
  2. 2The agent calls Cloudflare to enumerate Access apps and their grants.
  3. 3It queries the HR system of record through the custom MCP server for each identity's employment context.
  4. 4For each grant lacking a clean active match, the agent reasons over role, contractor flags, and rehire dates to assign a disposition with a rationale.
  5. 5It writes its dispositions and evidence to Postgres.
  6. 6It posts a prioritized findings summary to Slack for human approval.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect Custom MCP serverConnect any MCP-compatible tool you own.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.