Get complete inventory of all cloud flows (name, state, modified date). Lighter than scan-flow-health as it does not fetch run history.
AI agents call get-flow-inventory 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 retrieves information about cloud flows without modifying, deleting, or executing them. It is purely informational, querying flow inventory and metadata. There is no indication of the ability to trigger, modify, or delete flows. This falls squarely into the Read category as a safe, non-mutative operation.
From the tool's definition Tool description states 'Get complete inventory of all cloud flows (name, state, modified date)' and explicitly notes it is 'Lighter than scan-flow-health as it does not fetch run history.' The verb 'Get' and the stated retrieval of metadata (name, state,…
Documented attack patterns abuse exactly the kind of access get-flow-inventory 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-flow-inventory:
{
"version": "1",
"default": "deny",
"tools": {
"get-flow-inventory": {}
}
} get-flow-inventory 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 complete inventory of all cloud flows (name, state, modified date). Lighter than scan-flow-health as it does not fetch run history. 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-flow-inventory: 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-flow-inventory 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-flow-inventory 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-flow-inventory. 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-flow-inventory 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.