get_escrow
Inspect an escrow record by its 32-byte hex id.
This record as markdown: /tools/network-tenzro-tenzro/get-escrow.md
What get_escrow does on Tenzro Ledger MCP
AI agents call get_escrow 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.
Why get_escrow is rated Low
This tool retrieves and displays information about an existing escrow record identified by a hex ID. It performs no writes, deletions, financial transactions, or code execution—only data inspection, which is a Read operation. The low severity reflects that querying escrow record metadata poses minimal risk even if misused by an AI agent, as it cannot alter state or move funds.
From the tool's definition Tool name 'get_escrow' and description 'Inspect an escrow record' indicate data retrieval with no modification. The verb 'Inspect' is a read-only operation.
Attacks that exploit this kind of access
The rule that runs get_escrow 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 get_escrow, this is the rule to start with:
get_escrow is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every get_escrow call is checked against it from then on.
Questions about get_escrow
Inspect an escrow record by its 32-byte hex id. 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 get_escrow: 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.
get_escrow 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 get_escrow 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 get_escrow. 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.
get_escrow 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.
More on Tenzro Ledger, and thousands of servers like it.
This server
Across the catalogue