signed_agent_card_canonical_hash
AI agents call signed_agent_card_canonical_hash 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.
With an empty description, confidence is reduced. However, the naming pattern indicates a read-only operation that computes or retrieves a hash—typical of identity/verification operations in a ledger system. No evidence suggests data mutation, deletion, or financial transaction. The tool appears to be a lookup or derivation function rather than an action with side effects.
From the tool's definition Tool name 'signed_agent_card_canonical_hash' suggests retrieval or computation of a hash value for an agent card. The suffix '_hash' and 'canonical' imply a deterministic read operation that returns a digest or identifier.
Attacks that exploit this kind of access
signed_agent_card_canonical_hash. 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 signed_agent_card_canonical_hash: 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.
signed_agent_card_canonical_hash 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 signed_agent_card_canonical_hash 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 signed_agent_card_canonical_hash. 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.
signed_agent_card_canonical_hash 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 →