Get a specific classic workflow with its complete XAML definition or a structured summary
AI agents call get-workflow-definition 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 and queries workflow definitions and XAML content without creating, modifying, deleting, or executing workflows. It is purely informational access to workflow metadata, fitting the Read category. Severity is low because while workflow definitions may contain sensitive logic details, retrieving them does not directly impact system state or cause irreversible changes.
From the tool's definition Tool name 'get-workflow-definition' and description 'Get a specific classic workflow with its complete XAML definition or a structured summary' indicate retrieval of workflow metadata and definition.
Documented attack patterns abuse exactly the kind of access get-workflow-definition 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-workflow-definition:
{
"version": "1",
"default": "deny",
"tools": {
"get-workflow-definition": {}
}
} get-workflow-definition 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 a specific classic workflow with its complete XAML definition or a structured summary. 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-workflow-definition: 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-workflow-definition 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-workflow-definition 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-workflow-definition. 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-workflow-definition 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.