update_cloudflow_connection

SERVERDoit SOURCE@doitintl/doit-mcp-server

Medium RISK CLASS

Category Write

Parameters 82 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/update-cloudflow-connection.md

WHAT IT DOES

What update_cloudflow_connection does on Doit

AI agents use update_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	—	New connection name.
`enabled`	boolean	—	Set to false to disable the connection, true to re-enable it.
`ifMatch`	string	Yes	ETag from the connection's last read or write response (etag), including quotes. Sent as If-Match; a stale version fails with 412. Wildcards are rejected. The A
`awsConfig`	object	—	Full replacement AWS configuration, not a merge. At most one of gcpConfig or awsConfig may be set per request.
`gcpConfig`	object	—	Full replacement GCP configuration, not a merge. At most one of gcpConfig or awsConfig may be set per request.
`description`	string	—	New description for the connection.
`connectionId`	string	Yes	The ID of the CloudFlow connection to update (required).
`collaborators`	array	—	Full replacement list of collaborators and roles; retain exactly one owner. Omitted leaves unchanged; an empty list is invalid.

Parameters from the server's own tool schema.

RISK

Why update_cloudflow_connection is rated Medium

An AI agent can call update_cloudflow_connection faster than any human can review: one bad instruction and it creates or modifies resources in Doit by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (33 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_cloudflow_connection, this is the rule to start with:

update_cloudflow_connection Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_cloudflow_connection": {
      "limits": [
        {
          "counter": "update_cloudflow_connection_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every update_cloudflow_connection call is checked against it from then on.

FAQ

Questions about update_cloudflow_connection

What does the update_cloudflow_connection tool do? +

Updates a CloudFlow connection immediately using connectionId and the last observed ETag (ifMatch). A stale ETag fails with 412. Other fields are optional; supplied gcpConfig/awsConfig and collaborators replace their stored values wholesale. Retain exactly one owner when replacing collaborators. At most one provider config may be supplied. Serialize updates because the API version check is not atomic with the write. If an HTTP failure has only generic text, do not infer its status or retry automatically. 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.

What parameters does update_cloudflow_connection accept? +

update_cloudflow_connection accepts 8 parameters: name, enabled, ifMatch, awsConfig, gcpConfig, description, connectionId, collaborators. Required: ifMatch, connectionId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_cloudflow_connection? +

Register the Doit MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_cloudflow_connection? +

update_cloudflow_connection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_cloudflow_connection? +

Yes. Add a rate_limit block to the update_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.

How do I block update_cloudflow_connection completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_cloudflow_connection? +

update_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.

KEEP EXPLORING

More on Doit, and thousands of servers like it.

This server

All 238 Doit tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →