register_compliance
Register compliance rules for a token (KYC requirement, holder limits).
This record as markdown: /tools/network-tenzro-tenzro/register-compliance.md
What register_compliance does on Tenzro Ledger MCP
AI agents use register_compliance 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 register_compliance is rated Medium
This tool modifies token compliance metadata and governance parameters reversibly. While compliance rules affect behavior of financial instruments, the tool itself does not move money or commit financial obligations (Financial category). It does not irreversibly delete data (Destructive). It creates or updates compliance configuration, making it Write.
From the tool's definition Tool registers (creates/modifies) compliance rules for tokens, including KYC requirements and holder limits. The verb 'register' and the object 'compliance rules' indicate data creation or modification rather than deletion or financial movement.
Attacks that exploit this kind of access
The rule that runs register_compliance 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 register_compliance, this is the rule to start with:
register_compliance 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every register_compliance call is checked against it from then on.
Questions about register_compliance
Register compliance rules for a token (KYC requirement, holder limits). 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 register_compliance: 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.
register_compliance 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 register_compliance 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 register_compliance. 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.
register_compliance 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.
This server
Across the catalogue