Batch-scan all Power Automate cloud flows for health metrics. Fetches run history for each flow and computes success rates, failure counts. WARNING: batch operation that may take several minutes.
AI agents call scan-flow-health 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.
scan-flow-health performs read-only operations: fetching historical data and computing metrics. There are no side effects, state changes, or irreversible actions. The WARNING about duration reflects computational cost, not risk severity. This is a diagnostic/monitoring tool that queries existing flow metadata.
From the tool's definition Tool description states it 'Fetches run history for each flow and computes success rates, failure counts' — purely retrieval and analysis of existing telemetry data with no modification, deletion, or execution of flows.
Documented attack patterns abuse exactly the kind of access scan-flow-health 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 scan-flow-health:
{
"version": "1",
"default": "deny",
"tools": {
"scan-flow-health": {}
}
} scan-flow-health 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.
Batch-scan all Power Automate cloud flows for health metrics. Fetches run history for each flow and computes success rates, failure counts. WARNING: batch operation that may take several minutes. 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 scan-flow-health: 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.
scan-flow-health 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 scan-flow-health 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 scan-flow-health. 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.
scan-flow-health 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.