canton_submit_command
Submit a DAML create or exercise command.
This record as markdown: /tools/network-tenzro-tenzro/canton-submit-command.md
What canton_submit_command does on Tenzro Ledger MCP
AI agents invoke canton_submit_command 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 canton_submit_command is rated High
This tool submits commands to a DAML ledger, which executes create or exercise operations. These are active ledger state changes that trigger smart contract logic. The effects depend on the arguments passed (what contract is created or exercised), making this an Execute-category tool.
From the tool's definition Submit a DAML create or exercise command
Attacks that exploit this kind of access
The rule that runs canton_submit_command 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 canton_submit_command, this is the rule to start with:
canton_submit_command 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 canton_submit_command call is checked against it from then on.
Questions about canton_submit_command
Submit a DAML create or exercise command. 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 canton_submit_command: 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.
canton_submit_command 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 canton_submit_command 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 canton_submit_command. 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.
canton_submit_command 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