canton_grant_user_rights
AI agents use canton_grant_user_rights 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.
The name 'canton_grant_user_rights' strongly suggests this tool grants permissions or rights to users within a Canton (Daml/Canton ledger) system. Granting rights is a Write operation that modifies access control state. This carries high severity because misconfigured permissions could escalate privileges and expose sensitive financial/ledger data. Confidence is reduced due to the empty description.
From the tool's definition Tool name: canton_grant_user_rights — description is empty/uninformative.
Attacks that exploit this kind of access
canton_grant_user_rights. 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_grant_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_grant_user_rights 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_grant_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_grant_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_grant_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 →