Cloudflare Blog, read from an operations desk

Latest

Cloudflare's AI-agent browser adds WebMCP support and full automation API coverage

Cloudflare updated Kitesurf, its Workers-based browser built for AI agents, adding WebMCP support so sites can expose callable functions instead of requiring click-simulation, plus broader web-standard coverage (730,000+ WPT subtests) and full Browser Run API access via CDP, Playwright, Puppeteer or MCP. This makes agent-driven web browsing more reliable and cheaper to run.

What changes for operators — For a 10-200 person B2B company building or buying agents that need to pull data from websites, fill forms, or monitor competitor pages, this matters because WebMCP lets an agent call a site's exposed function (like searchFlights()) instead of guessing at pixels and DOM elements, cutting failure rates on brittle scraping workflows. Kitesurf also now works with standard tooling (Playwright, Puppeteer, MCP), so an ops or engineering team already using those frameworks for internal automation can swap in Kitesurf as the browser backend without rewriting scripts, and it's free during Cloudflare's beta behind per-account limits — worth testing before committing to a paid headless-browser vendor for agent workflows.

Cloudflare Lets Sites Block AI Training Without Losing AI Search Visibility

For a 10-200 person B2B company, this is a direct lever on lead generation through AI search. Buyers increasingly research vendors through ChatGPT, Perplexity, and AI Overviews rather than clicking blue links, so being retrievable and citable in those answers matters for pipeline. Until now, blocking AI crawlers to protect proprietary content (pricing pages, case studies, technical docs) also risked disappearing from AI-generated answers entirely. With this signal, an operator can tell crawlers: index and cite our content, but don't train on it. Marketing and RevOps teams should update robots.txt to declare this policy explicitly rather than relying on default crawler behavior, and should audit which AI bots (from OpenAI, Anthropic, Google, Perplexity) actually respect it, since compliance is voluntary.

Cloudflare Makes Python a First-Class Language for Building AI Agents on Its Edge Network

Most 10-200 person B2B companies won't touch this directly, but the teams and agencies that build their custom AI support bots, internal RAG search, or MCP-based assistants will feel it: Hyperdrive now lets a Python Worker query the company's existing PostgreSQL or MySQL database directly, and native langchain/openai support means an automation vendor can stand up a customer-facing AI agent or an internal knowledge assistant without maintaining a separate server or writing JavaScript adapters. For an operator evaluating build vs. buy on an AI support or ops tool, this lowers the engineering cost of a custom build running on Cloudflare's network, which is worth flagging to whichever contractor or in-house developer maintains your automation stack.

Cloudflare lets you cage AI agents to a single Worker

If your team runs agents or CI pipelines that deploy, debug, or monitor code on Cloudflare Workers, you can now give an agent a scoped API token that only reaches one application — say, your support-ticket webhook — rather than every Worker in the account. A misconfigured deployment script or a compromised agent token can no longer wander into your billing service or customer database Worker. For a 10-200 person company running several automated workflows on shared infrastructure, this turns

Cloudflare Adds AI-Driven Vulnerability Remediation to Managed Defense

For a 10-200 person B2B company running its site, API, or customer portal behind Cloudflare, this means vulnerability triage — usually a slow, manual task bounced between IT and a part-time security contractor — can now be partly automated. If your team already pays for Cloudflare's security tier, evaluate whether Managed Defense's new AI remediation reduces the need for a separate vulnerability-scanning vendor or manual patch review, since that's real budget and headcount time freed up for other ops work. Companies without dedicated security staff stand to gain the most, since the tool effectively acts as a junior security engineer that flags and proposes fixes automatically.

Cloudflare Opens Faster Verification Path for AI Bots and Agents

If your company's website sits behind Cloudflare, this directly affects how visible you are to AI search assistants like ChatGPT or Perplexity when prospects ask them for vendor recommendations. A verified bot listing means you can confidently allow specific AI crawlers through your firewall rules instead of blocking all bot traffic out of caution, which previously risked cutting your product pages, docs and pricing off from AI-generated answers. It also means unverified agents scraping your site under a fake identity are easier to identify and block, reducing wasted server load and the risk of automated abuse against contact forms or support chat.

Cloudflare Lets Sites Set AI Crawler Rules Once, Sync Everywhere

Most 10-200 person B2B companies run several web properties — marketing site, docs, blog, help center — often on different platforms, each needing separate bot rules to control AI crawler access. Bot Preference Sync means ops or marketing can set an AI access policy once (e.g., allow ChatGPT and Perplexity to cite content, block bots scraping for training) and have it apply consistently, without IT touching robots.txt on every subdomain. That matters directly for AI search visibility: getting cited correctly in AI Overviews or chatbot answers depends on crawlers being able to read the right pages while sensitive areas stay blocked. The catch is that sync only works where the receiving platform participates in Cloudflare's system, so it doesn't yet replace per-site vigilance everywhere content lives.

Cloudflare Narrows OAuth Consent to Specific Tasks, Cutting Agent Access Risk

If your sales or support team has wired an AI agent into a CRM, inbox or ticketing system through OAuth, that agent has probably been granted broad, standing permissions just to complete one narrow job, like drafting a reply or updating a deal stage. Task-based consent means you can start scoping agent access to the specific action being performed, so a compromised or misbehaving agent can't silently read or edit everything the connected account touches. For a 10-200 person company running several AI-driven integrations at once, this is the difference between a leaked token exposing one workflow versus exposing an entire mailbox or customer database, and it's worth auditing your existing OAuth grants once providers you use adopt this model.

Cloudflare Adds One-Click Login Gate for Internally Built Apps

If your ops, RevOps or support team has been using AI coding assistants to knock out quick internal dashboards, ticket triage tools, or data lookup apps on Cloudflare Workers, this closes a real exposure: those apps were often reachable by anyone with the URL, with no login screen, because nobody on a lean 10-200 person team owns "add auth" as a step. The one-click Access wrapper means a founder, ops lead or the person who vibe-coded the tool over a weekend can require company SSO login before the app loads, without writing any authentication code or asking a security engineer to intervene. Practically, this is worth an afternoon: audit every internally hosted Workers app your team has shipped in the last year, especially ones built with Claude, Cursor, or similar AI coding tools where speed took priority over security review, and put each one behind Access. It costs nothing extra in most Cloudflare plans and takes a few minutes per app. The broader lesson for lean teams is that AI coding tools lower the barrier to building internal software but do not lower the barrier to securing it — that gap has to be closed by infrastructure vendors or by a deliberate internal checklist, and this feature is one vendor closing it by default rather than leaving it to the builder to remember.

Solar Eclipse Briefly Dipped Internet Traffic Across Iceland, Spain, and Portugal

For a 10-200 person B2B company, this event carries no operational implication worth acting on. It is not a security incident, capacity risk, or infrastructure failure — it is a predictable, brief dip in regional consumer browsing behavior tied to a natural phenomenon. Unless your customer base is heavily concentrated in Reykjavik, Madrid, or Lisbon and your business depends on real-time traffic during a two-hour window on eclipse day, there is nothing here to change in your support staffing, uptime monitoring, or automation workflows. It's worth noting mainly as an example of how cleanly network telemetry can capture human behavior at scale — useful context if you ever need to explain an unexplained traffic anomaly to a client.

Cloudflare Adds Visibility and Controls for MCP Traffic Amid Rising Agent-to-Tool Connections

If your team has connected any AI agent — a support bot, a sales assistant, an internal ops tool — to external data sources or software using MCP, that traffic has likely been invisible to your IT or security stack until now. For a 10-200 person B2B company, this is rarely a dedicated security team's job to catch; it's usually whoever wired up the integration last quarter. The practical takeaway is not "adopt Cloudflare" — it's a prompt to ask your ops or engineering lead a direct question: which tools in our stack are making MCP connections, who authorized them, and can we see what data is flowing through them? If the answer is a shrug, that's the gap this announcement is surfacing.

Cloudflare Ships Certificate Transparency Monitoring to All Customers

For a 10-200 person B2B company, this is a quiet but useful upgrade to your security posture, not something that changes daily workflow. If your domains sit behind Cloudflare, you now get free, automatic notice if someone issues a certificate for your domain, support portal, or customer-facing subdomain without your knowledge — a common precursor to phishing campaigns targeting your customers or employees. The practical move is to confirm the feature is switched on and routed to whoever owns IT/security (often a founder or ops lead wearing multiple hats at this size), and to make sure alerts land somewhere that gets checked, not a dead inbox. This isn't a reason to change your automation stack or support workflows, but it's a legitimate, no-cost reduction in one specific risk: a spoofed certificate being used to impersonate your login page or API endpoints to your own customers.