High Risk →

resubmit_live_flow_run

Resubmit a failed or cancelled Power Automate flow run via the live PA API, re-using the original trigger payload. Discovers the trigger name from the flow definition automatically — no trigger name parameter needed.

Part of the Flow Studio - Power Automate MCP Server server.

resubmit_live_flow_run can trigger actions in Flow Studio - Power Automate MCP Server, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE FLOW STUDIO - POWER AUTOMATE MCP SERVER →

Free to start. No card required.

AI agents invoke resubmit_live_flow_run 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.

resubmit_live_flow_run 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "resubmit_live_flow_run": {
      "limits": [
        {
          "counter": "resubmit_live_flow_run_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Flow Studio - Power Automate MCP Server policy for all 33 tools.

Get this rule live on your own Flow Studio - Power Automate MCP Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY FLOW STUDIO - POWER AUTOMATE MCP SERVER →

View all 33 tools →

These attack patterns abuse exactly the kind of access resubmit_live_flow_run gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so resubmit_live_flow_run only ever does what you allow.

SECURE FLOW STUDIO - POWER AUTOMATE MCP SERVER →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the resubmit_live_flow_run tool do? +

Resubmit a failed or cancelled Power Automate flow run via the live PA API, re-using the original trigger payload. Discovers the trigger name from the flow definition automatically — no trigger name parameter needed.. 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.

How do I enforce a policy on resubmit_live_flow_run? +

Register the Flow Studio - Power Automate MCP Server MCP server in PolicyLayer and add a rule for resubmit_live_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 Flow Studio - Power Automate MCP Server. Nothing to install.

What risk level is resubmit_live_flow_run? +

resubmit_live_flow_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit resubmit_live_flow_run? +

Yes. Add a rate_limit block to the resubmit_live_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.

How do I block resubmit_live_flow_run completely? +

Set action: deny in the PolicyLayer policy for resubmit_live_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.

What MCP server provides resubmit_live_flow_run? +

resubmit_live_flow_run 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.

Enforce policy on every Flow Studio - Power Automate MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.