List the rights granted to a Canton user via
AI agents call canton_list_user_rights to retrieve information from Tenzro Ledger MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and displays user rights information without side effects. While it accesses permission/authorization data, listing existing rights is a read operation. Severity is low because exposing user rights information poses minimal immediate risk—it aids reconnaissance but does not enable direct privilege escalation or unauthorized actions by itself.
From the tool's definition Tool name contains 'list' (action: retrieval) and description states 'List the rights granted to a Canton user', indicating query/enumeration of existing permissions without modification.
Attacks that exploit this kind of access
List the rights granted to a Canton user via. It is categorised as a Read tool in the Tenzro Ledger MCP MCP Server, which means it retrieves data without modifying state.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for canton_list_user_rights: 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_list_user_rights is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the canton_list_user_rights 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_list_user_rights. 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_list_user_rights 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 →