List the published preset action-flow integration nodes (the dynamic TEMPLATE_CODE catalog — e.g. SMS, video/AI generation). Returns each template’s templateCodeId, displayName, group, async flag, and input/output param types. Pass a returned templateCodeId to schema tool-call ADD_ACTION_FLOW_NOD...
AI agents call list_actionflow_node_templates to retrieve information from Zion without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves metadata about available integration node templates from a server-managed catalog. It performs a read-only operation to enumerate preset configurations. There is no creation, modification, deletion, execution of arbitrary code, or financial impact.
From the tool's definition Tool description states it 'List the published preset action-flow integration nodes' and 'Returns each template's templateCodeId, displayName, group, async flag, and input/output param types.' The verb 'List' and 'Returns' indicate data retrieval with no…
Attacks that exploit this kind of access
List the published preset action-flow integration nodes (the dynamic TEMPLATE_CODE catalog — e.g. SMS, video/AI generation). Returns each template’s templateCodeId, displayName, group, async flag, and input/output param types. Pass a returned templateCodeId to schema tool-call ADD_ACTION_FLOW_NODE (TEMPLATE_CODE node) to insert it. The set is server-managed and changes over time, so query it rather than assuming a fixed provider. It is categorised as a Read tool in the Zion MCP Server, which means it retrieves data without modifying state.
Register the Zion MCP server in PolicyLayer and add a rule for list_actionflow_node_templates: 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.
list_actionflow_node_templates is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_actionflow_node_templates 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 list_actionflow_node_templates. 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.
list_actionflow_node_templates 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →