Get Power Automate cloud flows with smart filtering (excludes system, Copilot Sales, and Customer Insights flows by default)
AI agents call get-flows to retrieve information from PowerPlatform MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and lists Power Automate flows from the PowerPlatform system. It performs no modifications, deletions, executions, or financial operations. The smart filtering behavior is a query refinement, not a data-altering operation. Misuse would have minimal blast radius—an agent could discover flows but cannot modify, delete, or execute them with this tool alone.
From the tool's definition Tool name 'get-flows' and description 'Get Power Automate cloud flows with smart filtering' indicates a retrieval operation with no side effects. The description explicitly states it retrieves/queries flows without modification.
Documented attack patterns abuse exactly the kind of access get-flows gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PowerPlatform MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get-flows:
{
"version": "1",
"default": "deny",
"tools": {
"get-flows": {}
}
} get-flows is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get Power Automate cloud flows with smart filtering (excludes system, Copilot Sales, and Customer Insights flows by default). It is categorised as a Read tool in the PowerPlatform MCP MCP Server, which means it retrieves data without modifying state.
Register the PowerPlatform MCP server in PolicyLayer and add a rule for get-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 PowerPlatform MCP. Nothing to install.
get-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 get-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 get-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.
get-flows is provided by the PowerPlatform MCP server (michsob/powerplatform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PowerPlatform MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
66 PowerPlatform MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.