Upload a DAR (DAML Archive) to the participant via POST /v2/packages
AI agents use canton_upload_dar to create or update resources in Tenzro Ledger MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tenzro Ledger MCP environment.
This tool creates or uploads a DAML Archive package to a participant node, which is a reversible write operation that modifies the ledger infrastructure. It does not delete data (hence not Destructive), does not execute arbitrary code (hence not Execute in the narrow sense), and does not move funds (hence not Financial).
From the tool's definition Tool performs 'Upload a DAR (DAML Archive)' via POST /v2/packages, which is a create/upload operation that modifies the state of the participant by adding new DAML packages.
Attacks that exploit this kind of access
Upload a DAR (DAML Archive) to the participant via POST /v2/packages. It is categorised as a Write tool in the Tenzro Ledger MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for canton_upload_dar: 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_upload_dar 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 canton_upload_dar 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_upload_dar. 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_upload_dar 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.
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 →