list_cloudflows

Use this when the user wants to see their CloudFlow automation flows. Returns a cursor-paginated list of flows with their metadata, status, and last execution info.

SERVERDoit SOURCE@doitintl/doit-mcp-server

Low RISK CLASS

Category Read

Parameters 20 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/doit/list-cloudflows.md

WHAT IT DOES

What list_cloudflows does on Doit

AI agents call list_cloudflows to retrieve information from Doit without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`pageToken`	string	—	Pagination cursor returned by a previous call. Expires after five minutes.
`maxResults`	string	—	Maximum number of flows to return (1–500). Defaults to 50.

Parameters from the server's own tool schema.

RISK

Why list_cloudflows is rated Low

Even though list_cloudflows only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_cloudflows Allowed

list_cloudflows is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_cloudflows": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about list_cloudflows

What does the list_cloudflows tool do? +

Use this when the user wants to see their CloudFlow automation flows. Returns a cursor-paginated list of flows with their metadata, status, and last execution info. It is categorised as a Read tool in the Doit MCP Server, which means it retrieves data without modifying state.

What parameters does list_cloudflows accept? +

list_cloudflows accepts 2 parameters: pageToken, maxResults. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_cloudflows? +

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

list_cloudflows is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_cloudflows? +

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

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

list_cloudflows 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

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →