Edit server-side action flows — flows, nodes, branches, I/O, global variables, and triggers (scheduled / database-change). op is a schema ToolName; args is its payload. Call guide {plugin:"actionflow"} for the rules and arg shapes.
AI agents use actionflow to create or update resources in Zion — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zion environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
op | string | Yes | |
args | object | — | |
appExId | string | null | — | |
projectExId | string | — | |
appVersionExId | string | null | — |
Parameters from the server's own tool schema.
This tool creates or modifies server-side automation logic, making it a Write operation. While it could theoretically cascade into Execute or Destructive outcomes depending on what action flows are configured to do, the tool itself is fundamentally about configuration modification, not direct execution or deletion.
From the tool's definition Tool description states 'Edit server-side action flows' including 'flows, nodes, branches, I/O, global variables, and triggers'. The verb 'Edit' indicates modification of existing server-side configurations.
Attacks that exploit this kind of access
Edit server-side action flows — flows, nodes, branches, I/O, global variables, and triggers (scheduled / database-change). op is a schema ToolName; args is its payload. Call guide {plugin:"actionflow"} for the rules and arg shapes. It is categorised as a Write tool in the Zion MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
actionflow accepts 5 parameters: op, args, appExId, projectExId, appVersionExId. Required: op. The full parameter table on this page comes from the server's own tool schema.
Register the Zion MCP server in PolicyLayer and add a rule for actionflow: 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 Zion. Nothing to install.
actionflow is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the actionflow 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 actionflow. 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.
actionflow is provided by the Zion MCP server (zion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
actionflow is one line of Zion's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →