cloudflow_trigger
POST to a Power Automate Cloud Flow HTTP request URL. Works from any OS.
This record as markdown: /tools/io-github-heznpc-iconnect/cloudflow-trigger.md
What cloudflow_trigger does on Iconnect
AI agents invoke cloudflow_trigger to trigger actions in Iconnect. 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.
Why cloudflow_trigger is rated High
This tool triggers external automation workflows via HTTP POST, making it an Execute category risk. The 'blast radius' is high because an agent could POST to arbitrary Cloud Flow URLs with crafted payloads to trigger unintended automations, access control changes, data modifications, or other side effects in Power Automate and integrated systems (Office 365, Teams, SharePoint, etc.).
From the tool's definition Tool performs a POST request to an external API endpoint (Power Automate Cloud Flow), which executes workflows or automations whose effects depend on the target URL and payload arguments provided by the agent.
Attacks that exploit this kind of access
The rule that runs cloudflow_trigger safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cloudflow_trigger, this is the rule to start with:
cloudflow_trigger 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every cloudflow_trigger call is checked against it from then on.
Questions about cloudflow_trigger
POST to a Power Automate Cloud Flow HTTP request URL. Works from any OS. It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iconnect MCP server in PolicyLayer and add a rule for cloudflow_trigger: 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 Iconnect. Nothing to install.
cloudflow_trigger 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 cloudflow_trigger 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 cloudflow_trigger. 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.
cloudflow_trigger is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
Across the catalogue