List Power Automate flows in an environment. Returns id, displayName, state, triggerType, and lastModifiedTime for each flow. mode=owner (default): flows owned by the impersonated account, with full definition. mode=admin: all flows in the environment (requires an admin account). If search is pro...
Risk signalsAdmin/system-level operation
Part of the Flow Studio - Power Automate MCP Server server.
Free to start. No card required.
AI agents call list_live_flows to retrieve information from Flow Studio - Power Automate MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though list_live_flows only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"list_live_flows": {}
}
}See the full Flow Studio - Power Automate MCP Server policy for all 33 tools.
These attack patterns abuse exactly the kind of access list_live_flows gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
List Power Automate flows in an environment. Returns id, displayName, state, triggerType, and lastModifiedTime for each flow. mode=owner (default): flows owned by the impersonated account, with full definition. mode=admin: all flows in the environment (requires an admin account). If search is provided, results are filtered to flows whose displayName contains the search text. For large environments pagination is time-bounded — if nextLink is returned, pass it as continuationUrl to retrieve the next batch.. It is categorised as a Read tool in the Flow Studio - Power Automate MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Flow Studio - Power Automate MCP Server MCP server in PolicyLayer and add a rule for list_live_flows: 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 Flow Studio - Power Automate MCP Server. Nothing to install.
list_live_flows is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_live_flows 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 list_live_flows. 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.
list_live_flows is provided by the Flow Studio - Power Automate MCP Server MCP server (https://mcp.flowstudio.app/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 33 Flow Studio - Power Automate MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.