get_escrow_info

Get Escrow contract info — current fee, total deals created, treasury address, contract address. Use to verify the contract is live.

Server Base Escrow lordbasilaiassistant-sudo/base-escrow-mcp
Category Read
Risk class Low
Parameters 00 required

What get_escrow_info does on Base Escrow

AI agents call get_escrow_info 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.

Why get_escrow_info needs a policy

This tool retrieves blockchain contract metadata for informational purposes only. It has no side effects, cannot modify state, and poses minimal risk even if misused—an agent could only learn about the escrow contract's configuration. No financial transactions, code execution, or data destruction occurs.

From the tool's definition Tool description states 'Get Escrow contract info' and lists read-only outputs: 'current fee, total deals created, treasury address, contract address.' The verb 'Get' and the informational nature of the outputs (verification of contract status) indicate pure…

Questions about get_escrow_info

What does the get_escrow_info tool do? +

Get Escrow contract info — current fee, total deals created, treasury address, contract address. Use to verify the contract is live. It is categorised as a Read tool in the Base Escrow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_escrow_info? +

Register the Base Escrow MCP server in PolicyLayer and add a rule for get_escrow_info: 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.

What risk level is get_escrow_info? +

get_escrow_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_escrow_info? +

Yes. Add a rate_limit block to the get_escrow_info 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.

How do I block get_escrow_info completely? +

Set action: deny in the PolicyLayer policy for get_escrow_info. 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.

What MCP server provides get_escrow_info? +

get_escrow_info 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.