list_mandates

List the persisted AP2 mandates authorized by a controller DID.

SERVERTenzro Ledger MCP SOURCEhttps://canton-mcp.tenzro.network/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/network-tenzro-tenzro/list-mandates.md

WHAT IT DOES

What list_mandates does on Tenzro Ledger MCP

AI agents call list_mandates to retrieve information from Tenzro Ledger MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_mandates is rated Low

This tool queries and returns mandate data associated with a controller DID. It performs no modifications, deletions, or external state changes. The action is purely informational—listing persisted records. This fits the Read category pattern of 'search, list, get, fetch' operations.

From the tool's definition Tool name 'list_mandates' and description 'List the persisted AP2 mandates authorized by a controller DID' indicate a retrieval operation with no side effects. The verb 'list' is a query action that retrieves existing data about mandates.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_mandates 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 list_mandates, this is the rule to start with:

list_mandates Allowed

list_mandates is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_mandates": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every list_mandates call is checked against it from then on.

FAQ

Questions about list_mandates

What does the list_mandates tool do? +

List the persisted AP2 mandates authorized by a controller DID. It is categorised as a Read tool in the Tenzro Ledger MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_mandates? +

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

list_mandates is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_mandates? +

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

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

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

KEEP EXPLORING

More on Tenzro Ledger, and thousands of servers like it.

This server

All 360 Tenzro Ledger tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →