workflow_open
Open a multi-agent saga workflow. saga_steps is a list of
This record as markdown: /tools/network-tenzro-tenzro/workflow-open.md
What workflow_open does on Tenzro Ledger MCP
AI agents invoke workflow_open to trigger actions in Tenzro Ledger MCP. 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 workflow_open is rated High
Opening and orchestrating a multi-agent saga workflow triggers external operations across multiple agents. Given the server context (payments, staking, bridges, agents), executing a workflow could have broad side effects. The description is truncated, reducing confidence, but 'multi-agent saga workflow' strongly implies coordinated execution of complex steps rather than a simple read or write.
From the tool's definition Open a multi-agent saga workflow. `saga_steps` is a list of
Attacks that exploit this kind of access
The rule that runs workflow_open safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tenzro Ledger MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For workflow_open, this is the rule to start with:
workflow_open 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 Tenzro Ledger MCP, apply this rule, and every workflow_open call is checked against it from then on.
Questions about workflow_open
Open a multi-agent saga workflow. saga_steps is a list of. It is categorised as a Execute tool in the Tenzro Ledger MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for workflow_open: 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 Tenzro Ledger MCP. Nothing to install.
workflow_open 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 workflow_open 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 workflow_open. 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.
workflow_open is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tenzro Ledger, and thousands of servers like it.
Across the catalogue