create_cloudflow_connection
Use this when the user wants to create a new CloudFlow cloud provider connection (a GCP or AWS account connected for automation). Exactly one of gcpConfig or awsConfig must be supplied. Changes apply immediately. Do NOT use this to update an existing connection (use update_cloudflow_connection) o...
This record as markdown: /tools/doit/create-cloudflow-connection.md
What create_cloudflow_connection does on Doit
AI agents use create_cloudflow_connection to create or update resources in Doit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doit environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Human-readable connection name (required, non-empty). |
enabled | boolean | — | Whether the connection is enabled. Defaults to true. |
awsConfig | object | — | AWS configuration. Exactly one of gcpConfig or awsConfig must be supplied. |
gcpConfig | object | — | GCP configuration. Exactly one of gcpConfig or awsConfig must be supplied. |
description | string | — | Optional description of the connection. |
collaborators | array | — | List of collaborators and their roles on the connection. |
idempotencyKey | string | Yes | Idempotency-Key for this create attempt. Reuse the same key and body for retries within 24 hours; a different body with the same key fails with 422, an in-progr |
Parameters from the server's own tool schema.
Why create_cloudflow_connection is rated Medium
Creates reversible cloud provider connections enabling automated access to customer cloud infrastructure with immediate effect.
From the tool's definition create new CloudFlow cloud provider connection, GCP or AWS account connected for automation, changes apply immediately
Risk signalsHigh parameter count (32 properties)
Attacks that exploit this kind of access
The rule that runs create_cloudflow_connection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_cloudflow_connection, this is the rule to start with:
create_cloudflow_connection stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every create_cloudflow_connection call is checked against it from then on.
Questions about create_cloudflow_connection
Use this when the user wants to create a new CloudFlow cloud provider connection (a GCP or AWS account connected for automation). Exactly one of gcpConfig or awsConfig must be supplied. Changes apply immediately. Do NOT use this to update an existing connection (use update_cloudflow_connection) or to trigger a flow (use trigger_cloud_flow). It is categorised as a Write tool in the Doit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_cloudflow_connection accepts 7 parameters: name, enabled, awsConfig, gcpConfig, description, collaborators, idempotencyKey. Required: name, idempotencyKey. The full parameter table on this page comes from the server's own tool schema.
Register the Doit MCP server in PolicyLayer and add a rule for create_cloudflow_connection: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Doit. Nothing to install.
create_cloudflow_connection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_cloudflow_connection rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for create_cloudflow_connection. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
create_cloudflow_connection is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Doit, and thousands of servers like it.
This server
Across the catalogue