export_cloudflow_flow

SERVERDoit SOURCE@doitintl/doit-mcp-server

Medium RISK CLASS

Category Write

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/export-cloudflow-flow.md

WHAT IT DOES

What export_cloudflow_flow does on Doit

AI agents use export_cloudflow_flow 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
`flowId`	string	Yes
`customerContext`	string	—	Scope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users.
`includeVariableValues`	boolean	—

Parameters from the server's own tool schema.

RISK

Why export_cloudflow_flow is rated Medium

An AI agent can call export_cloudflow_flow 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 signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

export_cloudflow_flow Rate-limited

export_cloudflow_flow 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": {
    "export_cloudflow_flow": {
      "limits": [
        {
          "counter": "export_cloudflow_flow_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 export_cloudflow_flow call is checked against it from then on.

FAQ

Questions about export_cloudflow_flow

What does the export_cloudflow_flow tool do? +

Manage CloudFlow. Serializes the flow — plus every flow it references through subflow nodes — into a tenant-neutral, credential-free JSON bundle that can be imported into any tenant with the import operation. Tenant-scoped references (connections, Datastore tables, global variables) are declared as named requirements and rebound at import time; policy and Slack-channel references cannot travel and are recorded as unsupported references. The bundle never contains credentials, tenant identifiers, schedules, or execution state. codeNode: JavaScript (default) uses $nodes["<node name>"] and $variables; Python uses nodes and variables. Upstream values are lists. A top-level return produces {message: value}; no return gives JS {} / Python {message: null}. Bare input is not injected; accessing it as upstream data fails the node. A schema (JSON Schema string) is required. 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 export_cloudflow_flow accept? +

export_cloudflow_flow accepts 3 parameters: flowId, customerContext, includeVariableValues. Required: flowId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on export_cloudflow_flow? +

Register the Doit MCP server in PolicyLayer and add a rule for export_cloudflow_flow: 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 export_cloudflow_flow? +

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

Can I rate-limit export_cloudflow_flow? +

Yes. Add a rate_limit block to the export_cloudflow_flow 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 export_cloudflow_flow completely? +

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

export_cloudflow_flow 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

The MCP Attack Database →

Guides

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