Power Automate Debug

Debug failing Power Automate cloud flows using the FlowStudio MCP server. Load this skill when asked to: debug a flow, investigate a failed run, why is this...

This skill appears to do what it says: call FlowStudio MCP to inspect and (optionally) update Power Automate flows. Before installing or enabling it: 1) Confirm you trust FlowStudio (https://mcp.flowstudio.app) and that the FLOWSTUDIO_MCP_TOKEN you provide is from a trusted source. 2) Prefer a token scoped for the minimum needed permissions (read-only for diagnostics, separate write token for fixes) and with an expiration when possible. 3) Be mindful the skill includes steps that update and resubmit flows — only allow those actions if you trust the agent's capabilities and the token's privileges. 4) Because the skill is instruction-only, it won’t install local binaries, but the agent will make network calls to the external MCP endpoint; verify network governance and audit logs on the FlowStudio side. 5) If you want stricter control, require the agent to present proposed changes for manual approval before calling update_live_flow/resubmit_live_flow.

Type: OpenClaw Skill Name: power-automate-debug Version: 1.1.0 The skill bundle provides capabilities to diagnose and modify Power Automate flows via an external MCP server (mcp.flowstudio.app). It includes high-risk behaviors such as exfiltrating flow run outputs (which may contain sensitive data) and updating live flow definitions (update_live_flow in SKILL.md). While these capabilities are plausibly needed for the stated purpose of debugging and fixing flows, the combination of third-party network access and high-privilege write access to cloud infrastructure logic meets the criteria for a suspicious classification.