Get details of an escrow deal by its ID. Returns buyer, seller, token, amount, status, creation time, and description.
AI agents call get_deal to retrieve information from Base Escrow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and returns information about an existing escrow deal. It has no side effects, does not modify any state, and does not trigger any financial operations. Pure read operation with low blast radius.
From the tool's definition 'Get details of an escrow deal by its ID. Returns buyer, seller, token, amount, status, creation time, and description.'
Attacks that exploit this kind of access
Get details of an escrow deal by its ID. Returns buyer, seller, token, amount, status, creation time, and description. It is categorised as a Read tool in the Base Escrow MCP Server, which means it retrieves data without modifying state.
Register the Base Escrow MCP server in PolicyLayer and add a rule for get_deal: 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 Base Escrow. Nothing to install.
get_deal 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_deal 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_deal. 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_deal is provided by the Base Escrow MCP server (lordbasilaiassistant-sudo/base-escrow-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 →