register_identity · Tenzro Ledger MCP: Risk & Policy

WHAT IT DOES

What register_identity does on Tenzro Ledger MCP

AI agents use register_identity 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.

WHY IT NEEDS A POLICY

Why register_identity needs a policy

This tool creates or initializes a new identity entry, which is a Write operation—data is created and could theoretically be deleted or modified by subsequent operations. While identity registration has security implications (potential for impersonation or fraud if misused), the operation itself is reversible and does not execute code, delete data irreversibly, or move funds.

From the tool's definition Tool description states 'Register a new TDIP identity', which creates a new identity record in the system. The name 'register_identity' and verb 'Register' confirm a creation operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

register_identity Rate-limited

register_identity stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "register_identity": {
      "limits": [
        {
          "counter": "register_identity_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 register_identity

What does the register_identity tool do? +

Register a new TDIP identity. identity_type is 'human' or 'machine'. 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.

How do I enforce a policy on register_identity? +

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

register_identity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit register_identity? +

Yes. Add a rate_limit block to the register_identity 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 register_identity completely? +

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

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