Check the current status of an escrow transaction. Returns state (HELD, RELEASED, REFUNDED, DISPUTED), delivery status, and settlement details.
AI agents call check_escrow to retrieve information from Theagora MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves the status of an escrow transaction. It has no side effects—it does not create, modify, delete, or move funds. While the broader server involves financial transactions, this specific tool is read-only and performs a simple status lookup.
From the tool's definition Tool description states it 'Check[s] the current status of an escrow transaction' and 'Returns state...delivery status, and settlement details.' The verb is 'check' and the function is to retrieve and display information about an existing escrow, with no…
Attacks that exploit this kind of access
Check the current status of an escrow transaction. Returns state (HELD, RELEASED, REFUNDED, DISPUTED), delivery status, and settlement details. It is categorised as a Read tool in the Theagora MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Theagora MCP Server MCP server in PolicyLayer and add a rule for check_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 Theagora MCP Server. Nothing to install.
check_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 check_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 check_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.
check_escrow is provided by the Theagora MCP Server MCP server (theagoralabs/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 →