escrow_status

How much USDG and ETH waits in DomainEscrow on Robinhood Chain for a domain, and whether new deposits are paused. Funds wait there until the domain\

SERVER262 SOURCEType262/262

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/262/escrow-status.md

WHAT IT DOES

What escrow_status does on 262

AI agents call escrow_status to retrieve information from 262 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why escrow_status is rated Low

Even though escrow_status only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs escrow_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 262, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For escrow_status, this is the rule to start with:

escrow_status Allowed

escrow_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "escrow_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 262, apply this rule, and every escrow_status call is checked against it from then on.

FAQ

Questions about escrow_status

What does the escrow_status tool do? +

How much USDG and ETH waits in DomainEscrow on Robinhood Chain for a domain, and whether new deposits are paused. Funds wait there until the domain\. It is categorised as a Read tool in the 262 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on escrow_status? +

Register the 262 MCP server in PolicyLayer and add a rule for escrow_status: 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 262. Nothing to install.

What risk level is escrow_status? +

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

Can I rate-limit escrow_status? +

Yes. Add a rate_limit block to the escrow_status 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 escrow_status completely? +

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

escrow_status is provided by the 262 MCP server (Type262/262). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 262, and thousands of servers like it.

This server

All 4 262 tools →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →