Trigger an HTTP-triggered Power Automate flow by calling its live callback URL. Fetches the current signed trigger URL via the PA API (listCallbackUrl) then POSTs the provided body to it. If the flow trigger requires Azure Active Directory authentication, the impersonated Bearer token is automati...
Risk signalsAccepts raw HTML/template content (body)
Part of the Flow Studio - Power Automate MCP Server server.
Free to start. No card required.
AI agents invoke trigger_live_flow to trigger processes or run actions in Flow Studio - Power Automate MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
trigger_live_flow can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"trigger_live_flow": {
"limits": [
{
"counter": "trigger_live_flow_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Flow Studio - Power Automate MCP Server policy for all 33 tools.
These attack patterns abuse exactly the kind of access trigger_live_flow gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Trigger an HTTP-triggered Power Automate flow by calling its live callback URL. Fetches the current signed trigger URL via the PA API (listCallbackUrl) then POSTs the provided body to it. If the flow trigger requires Azure Active Directory authentication, the impersonated Bearer token is automatically included — no extra configuration needed. Returns the HTTP status, response body, requiresAadAuth flag, and authType. Only works for flows with a Request (HTTP) trigger type.. It is categorised as a Execute tool in the Flow Studio - Power Automate MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Flow Studio - Power Automate MCP Server MCP server in PolicyLayer and add a rule for trigger_live_flow: 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 Flow Studio - Power Automate MCP Server. Nothing to install.
trigger_live_flow 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 trigger_live_flow 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 trigger_live_flow. 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.
trigger_live_flow is provided by the Flow Studio - Power Automate MCP Server MCP server (https://mcp.flowstudio.app/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 33 Flow Studio - Power Automate MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.