# How to integrate Cloudflare MCP with Autogen ```json { "title": "How to integrate Cloudflare MCP with Autogen", "toolkit": "Cloudflare", "toolkit_slug": "cloudflare", "framework": "AutoGen", "framework_slug": "autogen", "url": "https://composio.dev/toolkits/cloudflare/framework/autogen", "markdown_url": "https://composio.dev/toolkits/cloudflare/framework/autogen.md", "updated_at": "2026-05-12T10:06:40.688Z" } ``` ## Introduction This guide walks you through connecting Cloudflare to AutoGen using the Composio tool router. By the end, you'll have a working Cloudflare agent that can add new a record for your domain, list all firewall rules for zone, show members of your cloudflare account through natural language commands. This guide will help you understand how to give your AutoGen agent real control over a Cloudflare account through Composio's Cloudflare MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Cloudflare with - [ChatGPT](https://composio.dev/toolkits/cloudflare/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/cloudflare/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/cloudflare/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/cloudflare/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/cloudflare/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/cloudflare/framework/codex) - [Cursor](https://composio.dev/toolkits/cloudflare/framework/cursor) - [VS Code](https://composio.dev/toolkits/cloudflare/framework/vscode) - [OpenCode](https://composio.dev/toolkits/cloudflare/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/cloudflare/framework/openclaw) - [Hermes](https://composio.dev/toolkits/cloudflare/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/cloudflare/framework/cli) - [Google ADK](https://composio.dev/toolkits/cloudflare/framework/google-adk) - [LangChain](https://composio.dev/toolkits/cloudflare/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/cloudflare/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/cloudflare/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/cloudflare/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/cloudflare/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get and set up your OpenAI and Composio API keys - Install the required dependencies for Autogen and Composio - Initialize Composio and create a Tool Router session for Cloudflare - Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams - Configure an Autogen AssistantAgent that can call Cloudflare tools - Run a live chat loop where you ask the agent to perform Cloudflare operations ## What is AutoGen? Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows. Key features include: - Multi-Agent Systems: Build collaborative agent workflows - MCP Workbench: Native support for Model Context Protocol tools - Streaming HTTP: Connect to external services through streamable HTTP - AssistantAgent: Pre-built agent class for tool-using assistants ## What is the Cloudflare MCP server, and what's possible with it? The Cloudflare MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Cloudflare account. It provides structured and secure access to your Cloudflare infrastructure, so your agent can perform actions like managing DNS records, configuring WAF lists, auditing firewall rules, and overseeing zones and account members—all on your behalf. - DNS record management: Effortlessly create or delete DNS records within any zone, allowing your agent to automate domain setup and maintenance tasks. - WAF list and firewall rule automation: Direct your agent to create, list, or delete Web Application Firewall (WAF) lists and audit firewall rules to enhance your site's security posture. - Zone administration: Enable your agent to create new zones when adding domains or delete zones that are no longer needed, streamlining domain onboarding and cleanup. - Account and member management: Let your agent list all Cloudflare accounts you have access to and enumerate members within each account for audit or collaboration purposes. - Comprehensive infrastructure visibility: Ask your agent to fetch and review your entire Cloudflare account structure, making it simple to monitor resources and configurations at scale. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `CLOUDFLARE_CREATE_DNS_RECORD` | Create DNS record | Tool to create a new DNS record within a specific zone. Requires write privileges and makes live changes to the zone. Use after obtaining the zone ID via CLOUDFLARE_LIST_ZONES to programmatically add DNS entries. | | `CLOUDFLARE_CREATE_LIST` | Create WAF List | Create a new empty custom list for use in WAF rules and filters. Lists can contain IP addresses, hostnames, ASNs, or redirects. Once created, use separate actions to add items to the list. Note: List availability depends on plan (Free: 1 list, Pro/Business: 10 lists, Enterprise: 1000 lists). Example: CREATE_LIST(account_id="abc123", kind="ip", name="blocklist", description="Block malicious IPs") | | `CLOUDFLARE_CREATE_ZONE` | Create Zone | Creates a new DNS zone (domain) in Cloudflare. A zone represents a domain and its DNS records. Use this when adding a new domain to manage with Cloudflare. Requires account ID (obtainable via LIST_ACCOUNTS). The zone will be in 'pending' status until nameservers are updated at the domain registrar. | | `CLOUDFLARE_DELETE_DNS_RECORD` | Delete DNS Record | Tool to delete a DNS record within a specific zone. Deletion is immediate and irreversible. Use only after confirming both zone and record IDs. Requires write privileges on the zone. Example: "Delete DNS record 372e6795... from zone 023e105f4ecef..." | | `CLOUDFLARE_DELETE_LIST` | Delete WAF List | Tool to delete a WAF list. Use when you need to remove a list after verifying no filters reference it. Example: DELETE_LIST(account_id="", list_id="") | | `CLOUDFLARE_DELETE_ZONE` | Delete Zone | Tool to delete a zone. Use after confirming the zone identifier to permanently remove a DNS zone and all its DNS records from your Cloudflare account. Example: DELETE_ZONE(zone_identifier="023e105f4ecef8ad9ca31a8372d0c353") | | `CLOUDFLARE_GET_BOT_MANAGEMENT_SETTINGS` | Get Bot Management Settings | Tool to retrieve a zone's Bot Management configuration (Bot Fight Mode / Super Bot Fight Mode / Enterprise Bot Management). Use after identifying the correct zone_id (e.g., via CLOUDFLARE_LIST_ZONES). This tool is the canonical way to audit bot-related configuration; firewall rules are adjacent controls but not equivalent to Bot Management settings. | | `CLOUDFLARE_GET_LISTS` | List WAF Lists | Tool to fetch all WAF lists (no items) for an account. Results are paginated; iterate using page and per_page parameters until result_info.total_pages is reached to retrieve all lists. Use after confirming account ID. | | `CLOUDFLARE_LIST_ACCOUNT_MEMBERS` | List Account Members | Lists all members of a Cloudflare account with their roles, permissions, and status. Returns detailed information about each account member including their user details (name, email, 2FA status), assigned roles with granular permissions, membership status (accepted/pending/rejected), and access policies. Supports filtering by status, sorting by various fields, and pagination for accounts with many members. Use this action when you need to: - View all users with access to a Cloudflare account - Audit account member permissions and roles - Check membership status of invited users - List members with specific roles or statuses Requires the account ID which can be obtained using the List Accounts action. Note: caller's account role may restrict visibility of some members if permissions are insufficient. | | `CLOUDFLARE_LIST_ACCOUNTS` | List Accounts | List all Cloudflare accounts you have ownership or verified access to. Retrieves a paginated list of accounts with their details including account ID, name, type, settings, and creation date. An empty or partial result may indicate insufficient API token scope or permissions, not the absence of accounts. When multiple accounts are returned, confirm the intended account_id before performing any write operations to avoid acting on unintended environments. Use this when you need to: - Discover available accounts before performing account-specific operations - Find an account ID for other API calls that require an account identifier - Audit account configurations and settings - Filter accounts by name or paginate through large account lists | | `CLOUDFLARE_LIST_DNS_RECORDS` | List DNS records | Tool to list and search DNS records in a Cloudflare zone. Use when you need to find existing DNS record IDs for update or delete operations, especially after a "record already exists" error during creation. Returns matching records with their IDs, names, types, content, and other properties. | | `CLOUDFLARE_LIST_FIREWALL_RULES` | List Firewall Rules | Tool to list firewall rules for a specific DNS zone. Use after confirming the zone ID to retrieve and audit current firewall rules. Does not expose Workers routes or other routing constructs. | | `CLOUDFLARE_LIST_MONITORS` | List Monitors | Tool to list all load-balancer monitors in a Cloudflare account. Use after creating or updating monitors to retrieve a paginated list. Response includes `result_info.total_pages` to determine when all pages have been fetched. | | `CLOUDFLARE_LIST_POOLS` | List Pools | Tool to list all load balancer pools in a Cloudflare account. Use after confirming account ID to discover pool IDs. Paginate using `page` and `per_page`; check `result_info.total_pages` in the response to determine if additional pages exist. | | `CLOUDFLARE_LIST_TUNNELS` | List Tunnels | List Cloudflare Tunnel (cloudflared) tunnels in an account to discover tunnel IDs, names, and statuses. Use when you need to find a tunnel_id before performing tunnel operations like routing, DNS configuration, or debugging. | | `CLOUDFLARE_LIST_ZONES` | List Zones | Lists, searches, sorts, and filters zones in the authenticated account. Use `page`/`per_page` to paginate; check `result_info.total_pages` in the response to iterate all pages. Does not return DNS records — extract `zone_id` from results before passing to zone-scoped tools (DNS, firewall, etc.). Only zones delegated to Cloudflare nameservers appear; empty results indicate scope or delegation constraints, not errors. | | `CLOUDFLARE_UPDATE_DNS_RECORD` | Update DNS record | Tool to update an existing DNS record within a specific zone. Use after confirming both zone and record identifiers; only provided fields are modified. Updates to records used by active tunnels take effect immediately and can disrupt live traffic. | | `CLOUDFLARE_UPDATE_LIST` | Update WAF List | Tool to update the description of a WAF list (cannot update items). Use after confirming list metadata. | | `CLOUDFLARE_UPDATE_TUNNEL_CONFIGURATION` | Update Tunnel Configuration | Tool to update a remotely-managed Cloudflare Tunnel's configuration (ingress rules and routing). Use when you need to programmatically configure hostname-to-origin mappings for a tunnel. WARNING: This operation REPLACES the entire configuration - incorrect configuration can break routing and make services unreachable. Best practice: fetch current configuration first (if patching) to preserve existing rules. At least one ingress rule is required, and the last rule should typically be a catch-all (hostname='*' or omitted) with service='http_status:404'. | | `CLOUDFLARE_UPDATE_ZONE` | Update Zone | Tool to update properties of an existing zone; changes apply immediately to the live zone. Confirm zone ID and intended change with the user before calling. Only one field can be modified per call. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Cloudflare MCP server is an implementation of the Model Context Protocol that connects your AI agents and assistants directly to Cloudflare. Instead of manually wiring Cloudflare APIs, OAuth, and scopes yourself, you get a structured, tool-based interface that an LLM can call safely. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites You will need: - A Composio API key - An OpenAI API key (used by Autogen's OpenAIChatCompletionClient) - A Cloudflare account you can connect to Composio - Some basic familiarity with Autogen and Python async ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) and create an API key. You'll need credits to use the models, or you can connect to another model provider. - Keep the API key safe. Composio API Key - Log in to the [Composio dashboard](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install dependencies Install Composio, Autogen extensions, and dotenv. What's happening: - composio connects your agent to Cloudflare via MCP - autogen-agentchat provides the AssistantAgent class - autogen-ext-openai provides the OpenAI model client - autogen-ext-tools provides MCP workbench support ```bash pip install composio python-dotenv pip install autogen-agentchat autogen-ext-openai autogen-ext-tools ``` ### 3. Set up environment variables Create a .env file in your project folder. What's happening: - COMPOSIO_API_KEY is required to talk to Composio - OPENAI_API_KEY is used by Autogen's OpenAI client - USER_ID is how Composio identifies which user's Cloudflare connections to use ```bash COMPOSIO_API_KEY=your-composio-api-key OPENAI_API_KEY=your-openai-api-key USER_ID=your-user-identifier@example.com ``` ### 4. Import dependencies and create Tool Router session What's happening: - load_dotenv() reads your .env file - Composio(api_key=...) initializes the SDK - create(...) creates a Tool Router session that exposes Cloudflare tools - session.mcp.url is the MCP endpoint that Autogen will connect to ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Cloudflare session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["cloudflare"] ) url = session.mcp.url ``` ### 5. Configure MCP parameters for Autogen Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for. What's happening: - url points to the Tool Router MCP endpoint from Composio - timeout is the HTTP timeout for requests - sse_read_timeout controls how long to wait when streaming responses - terminate_on_close=True cleans up the MCP server process when the workbench is closed ```python # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) ``` ### 6. Create the model client and agent What's happening: - OpenAIChatCompletionClient wraps the OpenAI model for Autogen - McpWorkbench connects the agent to the MCP tools - AssistantAgent is configured with the Cloudflare tools from the workbench ```python # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Cloudflare assistant agent with MCP tools agent = AssistantAgent( name="cloudflare_assistant", description="An AI assistant that helps with Cloudflare operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) ``` ### 7. Run the interactive chat loop What's happening: - The script prompts you in a loop with You: - Autogen passes your input to the model, which decides which Cloudflare tools to call via MCP - agent.run_stream(...) yields streaming messages as the agent thinks and calls tools - Typing exit, quit, or bye ends the loop ```python print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Cloudflare related question or task to the agent.\n") # Conversation loop while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, "content") and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") ``` ## Complete Code ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Cloudflare session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["cloudflare"] ) url = session.mcp.url # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Cloudflare assistant agent with MCP tools agent = AssistantAgent( name="cloudflare_assistant", description="An AI assistant that helps with Cloudflare operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Cloudflare related question or task to the agent.\n") # Conversation loop while True: user_input = input("You: ").strip() if user_input.lower() in ['exit', 'quit', 'bye']: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, 'content') and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") if __name__ == "__main__": asyncio.run(main()) ``` ## Conclusion You now have an Autogen assistant wired into Cloudflare through Composio's Tool Router and MCP. From here you can: - Add more toolkits to the toolkits list, for example notion or hubspot - Refine the agent description to point it at specific workflows - Wrap this script behind a UI, Slack bot, or internal tool Once the pattern is clear for Cloudflare, you can reuse the same structure for other MCP-enabled apps with minimal code changes. ## How to build Cloudflare MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/cloudflare/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/cloudflare/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/cloudflare/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/cloudflare/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/cloudflare/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/cloudflare/framework/codex) - [Cursor](https://composio.dev/toolkits/cloudflare/framework/cursor) - [VS Code](https://composio.dev/toolkits/cloudflare/framework/vscode) - [OpenCode](https://composio.dev/toolkits/cloudflare/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/cloudflare/framework/openclaw) - [Hermes](https://composio.dev/toolkits/cloudflare/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/cloudflare/framework/cli) - [Google ADK](https://composio.dev/toolkits/cloudflare/framework/google-adk) - [LangChain](https://composio.dev/toolkits/cloudflare/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/cloudflare/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/cloudflare/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/cloudflare/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/cloudflare/framework/crew-ai) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [Anchor browser](https://composio.dev/toolkits/anchor_browser) - Anchor browser is a developer platform for AI-powered web automation. It transforms complex browser actions into easy API endpoints for streamlined web interaction. - [Apiflash](https://composio.dev/toolkits/apiflash) - Apiflash is a website screenshot API for programmatically capturing web pages. It delivers high-quality screenshots on demand for automation, monitoring, or reporting. - [Apiverve](https://composio.dev/toolkits/apiverve) - Apiverve delivers a suite of powerful APIs that simplify integration for developers. It's designed for reliability and scalability so you can build faster, smarter applications without the integration headache. - [Appcircle](https://composio.dev/toolkits/appcircle) - Appcircle is an enterprise-grade mobile CI/CD platform for building, testing, and publishing mobile apps. It streamlines mobile DevOps so teams ship faster and with more confidence. - [Appdrag](https://composio.dev/toolkits/appdrag) - Appdrag is a cloud platform for building websites, APIs, and databases with drag-and-drop tools and code editing. It accelerates development and iteration by combining hosting, database management, and low-code features in one place. - [Appveyor](https://composio.dev/toolkits/appveyor) - AppVeyor is a cloud-based continuous integration service for building, testing, and deploying applications. It helps developers automate and streamline their software delivery pipelines. - [Backendless](https://composio.dev/toolkits/backendless) - Backendless is a backend-as-a-service platform for mobile and web apps, offering database, file storage, user authentication, and APIs. It helps developers ship scalable applications faster without managing server infrastructure. - [Baserow](https://composio.dev/toolkits/baserow) - Baserow is an open-source no-code database platform for building collaborative data apps. It makes it easy for teams to organize data and automate workflows without writing code. - [Bench](https://composio.dev/toolkits/bench) - Bench is a benchmarking tool for automated performance measurement and analysis. It helps you quickly evaluate, compare, and track your systems or workflows. - [Better stack](https://composio.dev/toolkits/better_stack) - Better Stack is a monitoring, logging, and incident management solution for apps and services. It helps teams ensure application reliability and performance with real-time insights. - [Bitbucket](https://composio.dev/toolkits/bitbucket) - Bitbucket is a Git-based code hosting and collaboration platform for teams. It enables secure repository management and streamlined code reviews. - [Blazemeter](https://composio.dev/toolkits/blazemeter) - Blazemeter is a continuous testing platform for web and mobile app performance. It empowers teams to automate and analyze large-scale tests with ease. - [Blocknative](https://composio.dev/toolkits/blocknative) - Blocknative delivers real-time mempool monitoring and transaction management for public blockchains. Instantly track pending transactions and optimize blockchain interactions with live data. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Cloudflare MCP? With a standalone Cloudflare MCP server, the agents and LLMs can only access a fixed set of Cloudflare tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Cloudflare and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Autogen? Yes, you can. Autogen fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Cloudflare tools. ### Can I manage the permissions and scopes for Cloudflare while using Tool Router? Yes, absolutely. You can configure which Cloudflare scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Cloudflare data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)