Verify a Tenzro DID envelope passed as a hex header value (the
AI agents call verify_did_envelope 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.
This tool performs cryptographic verification of a DID envelope, which is a read-only operation that checks the validity of an identity credential. It retrieves/validates data without creating, modifying, deleting, or executing arbitrary code. The blast radius of misuse is limited to potentially accepting invalid DIDs, which is a low-severity concern in an authentication context.
From the tool's definition Tool name 'verify_did_envelope' and description context indicate verification of a DID (Decentralized Identifier) envelope cryptographic structure.
Attacks that exploit this kind of access
Verify a Tenzro DID envelope passed as a hex header value (the. 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 verify_did_envelope: 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.
verify_did_envelope 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 verify_did_envelope 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 verify_did_envelope. 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.
verify_did_envelope 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 →