Cancel a running or waiting flow run. Cannot cancel flows already in a terminal state (Succeeded, Failed, Cancelled).
AI agents invoke cancel-flow-run to trigger actions in PowerPlatform MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Cancelling a flow run terminates an active process mid-execution. While it doesn't delete data, it interrupts an external operation (a running flow) whose effects depend on the specific flow being cancelled. This is an irreversible interruption of an ongoing operation — once cancelled, the flow run cannot be resumed.
From the tool's definition Cancel a running or waiting flow run
Documented attack patterns abuse exactly the kind of access cancel-flow-run 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 cancel-flow-run:
{
"version": "1",
"default": "deny",
"tools": {
"cancel-flow-run": {
"limits": [
{
"counter": "cancel-flow-run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} cancel-flow-run stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Cancel a running or waiting flow run. Cannot cancel flows already in a terminal state (Succeeded, Failed, Cancelled). It is categorised as a Execute tool in the PowerPlatform MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PowerPlatform MCP server in PolicyLayer and add a rule for cancel-flow-run: 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.
cancel-flow-run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cancel-flow-run 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 cancel-flow-run. 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.
cancel-flow-run 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.