Run or inspect named flows defined in ue-mcp.yml. Config is reloaded on every call — no restart needed. Actions: - run: Execute a flow. Params: flowName, skip?, params?, rollback_on_failure? - plan: Show execution plan without running. Params: flowName - list: List available flows Step types su...
Bulk/mass operation — affects multiple targets
Part of the Ue MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke flow to trigger processes or run actions in Ue. 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.
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. Intercept 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.
tools:
flow:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Ue policy for all 20 tools.
Agents calling execute-class tools like flow have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
flow is one of the high-risk operations in Ue. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Run or inspect named flows defined in ue-mcp.yml. Config is reloaded on every call — no restart needed. Actions: - run: Execute a flow. Params: flowName, skip?, params?, rollback_on_failure? - plan: Show execution plan without running. Params: flowName - list: List available flows Step types supported in YAML flows: any MCP action (category.action), nested flows (flow:), and 'shell' for running shell/exec commands. Example shell step: steps: 1: { task: shell, options: { command: "npm run up:build" } } params: Runtime options merged into every step's options (highest priority). Use to override YAML-hardcoded values like levelPath, directory, configuration, etc. rollback_on_failure: When true, rollback records from completed steps are invoked in reverse order if a subsequent step fails.. It is categorised as a Execute tool in the Ue MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for flow. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ue MCP server.
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 flow rule in your Intercept 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 Intercept policy for 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.
flow is provided by the Ue MCP server (ue-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept