Cloudflare adds per-agent visibility and access policies for personal agents
Cloudflare announced analytics that identify personal-agent traffic and controls that apply separate access policies to supported agents.
AT A GLANCE
Key points
- Security Analytics can display personal-agent traffic as a separate category.
- Sites can set a different access policy for each supported agent.
- Early-access account protection links some events with the agent and represented user.
What is changing?
Cloudflare launched analytics that show personal AI agent traffic as a separate category and per-agent access policies on November 4. Bot Analysis in Security Analytics can now display a Personal Assistants class, while Top statistics separates which agent sent requests, the paths it accessed and the status codes it received.
Sites using the early-access version of Account Abuse Protection can see which user an agent represents for certain login and sign-up events. Security teams can review an agent’s use across accounts and, when needed, apply a WAF rule through a hashed user identifier.
In AI Crawler and Agent access policies, sites can supplement the overall Agents policy with Allow, Block on pages with ads or Block for each supported agent. Production teams should separately monitor misclassification, user privacy and whether agent identity is actually verified.
Explore the original sources
Source date: 4 November 2026.
Published by AI Radar: 4 Nov 2026, 18:14 (Istanbul, UTC+3).
FOLLOW THE TOPIC
Topics and tags
Share your discovery.
Send this story to a friend.
Reader comments
What do you think about this development? Share your experience or question. Comments are published after editorial approval.
Your name/nickname and comment become public if approved. Read: Privacy notice.
Loading comments…