resolve_username

Resolve a username to its associated DID and identity info.

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/resolve-username.md

WHAT IT DOES

What resolve_username does on Tenzro Ledger MCP

AI agents call resolve_username 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 resolve_username is rated Low

This tool performs a lookup/query operation, resolving a username to identity information. It retrieves existing data without creating, modifying, or deleting anything. Severity is low as it only reads public identity/DID information.

From the tool's definition Resolve a username to its associated DID and identity info

Attacks that exploit this kind of access

RECOMMENDED RULE

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

resolve_username Allowed

resolve_username 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": {
    "resolve_username": {}
  }
}

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 resolve_username call is checked against it from then on.

FAQ

Questions about resolve_username

What does the resolve_username tool do? +

Resolve a username to its associated DID and identity info. 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 resolve_username? +

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

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

Can I rate-limit resolve_username? +

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

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

resolve_username 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

The MCP Attack Database →

Guides

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