Responsible AI — Flow Studio MCP

1 Our Approach

Flow Studio MCP is built on privacy-by-design and data minimization principles. We collect only what is needed to authenticate requests, enforce plan limits, and operate the service. We do not collect or process data beyond what is required to provide the MCP tools you use.

Flow Studio MCP is a third-party service — it is not built, endorsed, or operated by Microsoft. It connects to Microsoft Power Platform APIs using your delegated consent, subject to your organisation’s policies.

2 What We Don’t Access

Flow Studio MCP requests only the Power Platform scopes needed to read and manage flows. We have no access to your mailbox, calendar, files, or SharePoint. We do not store flow definitions, action payloads, connection secrets, or run output data. See our Security page for the full authentication model and scope details.

3 AI Agent Transparency

Flow Studio MCP provides tools, not autonomous AI. When your AI agent (Claude, Copilot, ChatGPT, or any MCP client) calls an MCP tool:

The call is made in your security context using your delegated Microsoft consent. It is subject to your tenant’s RBAC and DLP policies.
Flow Studio does not decide which tools to call or when. The AI agent decides; Flow Studio executes the requested operation.
No server-side AI — Flow Studio MCP does not run any AI model or large language model on its own servers. It is a structured API layer between your AI agent and the Power Platform APIs.

4 How We Use Error Data to Improve the Service

We analyse error patterns from MCP tool calls — such as common API error codes, malformed inputs, and frequent failure modes — to improve the service. This includes:

Input validation — detecting and flagging common input mistakes before requests are sent to the Power Automate API
Clearer error guidance — providing actionable information when tools return errors, so agents can self-correct

What this uses: error metadata, HTTP status codes, tool names, and error message patterns.

What this does not use: your flow business logic, action payload content, connection secrets, or run output data.

We do not send your data to third-party AI models for training.

5 Human-in-the-Loop

Flow Studio MCP is designed so that users remain in control:

Explicit consent — you grant Power Platform access through Microsoft’s standard OAuth consent flow. You can revoke access at any time from your dashboard or from myapps.microsoft.com.
Monitoring is opt-in — Pro+ store tools that cache flow metadata require you to explicitly opt in per flow. Flows are not automatically scanned or cached.
Write operations are logged — tools that modify or trigger live flows are logged for auditability.

We recommend that users review and approve agent-driven changes before applying them to production flows. Flow Studio provides the tools; the decision to act should remain with the user or an approved workflow.

6 Third-Party AI Clients

Flow Studio MCP is a tool provider. The AI clients that call our tools — such as Claude, GitHub Copilot, ChatGPT, or Microsoft Copilot Studio — are operated by their respective companies. Flow Studio does not control how these clients process, store, or use the responses they receive from our tools. Please refer to each client’s own privacy and AI policies for details.

7 Related Pages

Security

Authentication model, token storage, data retention, and incident response.

What data we collect, how we use it, third-party services, and your rights.

Personal Data (cross-product)

How personal data is handled across all Flow Studio products.

? Questions

For questions about our responsible AI practices, data handling, or to request information for a compliance review, contact [email protected].