spraay_escrow_get
Get full escrow details including status, participants, conditions, balance check, and timestamps by ID. Data persists in Supabase. Costs $0.001 USDC.
This record as markdown: /tools/io-github-plagtech-spraay-x402-mcp/spraay-escrow-get.md
What spraay_escrow_get does on Spraay X402 Mcp
AI agents call spraay_escrow_get to retrieve information from Spraay X402 Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why spraay_escrow_get is rated Low
The tool retrieves and queries escrow data from Supabase without modifying, deleting, or executing operations. While it operates in a crypto/DeFi context and has a cost, the cost is metered access to a read operation, not a financial transaction (no money moves between accounts). The blast radius of misuse is limited to unauthorized data access of escrow details.
From the tool's definition Tool name contains 'get' and description states 'Get full escrow details including status, participants, conditions, balance check, and timestamps by ID.' This is a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs spraay_escrow_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Spraay X402 Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spraay_escrow_get, this is the rule to start with:
spraay_escrow_get 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 Spraay X402 Mcp, apply this rule, and every spraay_escrow_get call is checked against it from then on.
Questions about spraay_escrow_get
Get full escrow details including status, participants, conditions, balance check, and timestamps by ID. Data persists in Supabase. Costs $0.001 USDC. It is categorised as a Read tool in the Spraay X402 Mcp MCP Server, which means it retrieves data without modifying state.
Register the Spraay X402 MCP server in PolicyLayer and add a rule for spraay_escrow_get: 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 Spraay X402 Mcp. Nothing to install.
spraay_escrow_get 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 spraay_escrow_get 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 spraay_escrow_get. 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.
spraay_escrow_get is provided by the Spraay X402 MCP server (spraay-x402-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Spraay X402, and thousands of servers like it.
This server
Across the catalogue