Discuss your project
Web architecture

Cloudflare OS: check what an agent can read in connected tools

Your team wants a report drawn from two tools. Test which workspaces the connector can read, what gets logged and whether revoking a permission stops the task.

Cloudflare OS : vérifier ce qu’un agent peut lire dans vos outils

A team wants to summarize project tickets and documents for Monday. It needs to show which spaces the connector could reach. On October 19, 2026, Cloudflare announced new integrations and deployment partners for its AI workspace, Cloudflare OS, including Asana, Box, GitHub and Notion. On October 1, its blog distinguished deployment into your Cloudflare account from a fully managed waitlisted offer. Confirm current capabilities and terms in your environment.

Test with your own data

Make two demo spaces per tool and three accounts, one without access to the second space. Connect an account with limited read access. Check that the agent only returns content from the first space, including when the second has a similar name. Revoke access during a new run and inspect the result and logs. Record identity, tool, access decision and time to enforcement. If the check fails, pause the workflow and review previously stored outputs.

Making a decision

Start with a connector whose permissions, logs and revocation you can verify. Keep a manual process and an export format. Our business agent article covers authorization in general. This trial focuses on the scope and exit path of a specific Cloudflare OS connector.

Share this article