submit_daml_create · Tenzro Ledger MCP: Risk & Policy

WHAT IT DOES

What submit_daml_create does on Tenzro Ledger MCP

AI agents invoke submit_daml_create 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 IT NEEDS A POLICY

Why submit_daml_create needs a policy

This tool executes a DAML create command on a shared Canton distributed ledger domain. While 'create' implies writing new data, submitting commands to a distributed ledger/smart contract platform is an Execute-level action — it triggers external blockchain/ledger operations with potentially irreversible on-chain effects.

From the tool's definition Submit a DAML ``create`` command on the shared Canton domain

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_daml_create Rate-limited

submit_daml_create 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_daml_create": {
      "limits": [
        {
          "counter": "submit_daml_create_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tenzro Ledger MCP, so you can run agents against it safely.

FAQ

Questions about submit_daml_create

What does the submit_daml_create tool do? +

Submit a DAML create command on the shared Canton domain. 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.

How do I enforce a policy on submit_daml_create? +

Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for submit_daml_create: 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.

What risk level is submit_daml_create? +

submit_daml_create is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit submit_daml_create? +

Yes. Add a rate_limit block to the submit_daml_create 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.

How do I block submit_daml_create completely? +

Set action: deny in the PolicyLayer policy for submit_daml_create. 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.

What MCP server provides submit_daml_create? +

submit_daml_create 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.