New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

sap_fetch_escrow_v2

Fetch a V2 escrow by escrow PDA, or by agent PDA, depositor, and nonce. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts. SAP MCP exe...

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-fetch-escrow-v2.md

What sap_fetch_escrow_v2 does on Sap

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

ParameterTypeRequiredDescription
nonce number Escrow nonce (default: 0) — used with agentPda and depositor
agentPda string Agent PDA (base58) — used when escrowPda is omitted
depositor string Optional depositor wallet (base58) to filter by
escrowPda string Escrow V2 PDA (base58) to fetch directly

Parameters from the server's own tool schema.

Why sap_fetch_escrow_v2 is rated Low

Tool retrieves blockchain escrow data without modifications or side effects.

From the tool's definition Fetch a V2 escrow by escrow PDA, read-only SAP SDK wrapper, inspect current chain state.

Questions about sap_fetch_escrow_v2

What does the sap_fetch_escrow_v2 tool do? +

Fetch a V2 escrow by escrow PDA, or by agent PDA, depositor, and nonce. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program. Use these reads to inspect current chain state before mutating registry, payment, reputation, memory, or tool accounts. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: paid read-premium; estimate first, then use sap_payments_call_paid_tool when the runtime cannot replay x402 natively. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required. It is categorised as a Read tool in the Sap MCP Server, which means it retrieves data without modifying state.

What parameters does sap_fetch_escrow_v2 accept? +

sap_fetch_escrow_v2 accepts 4 parameters: nonce, agentPda, depositor, escrowPda. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_fetch_escrow_v2? +

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

What risk level is sap_fetch_escrow_v2? +

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

Can I rate-limit sap_fetch_escrow_v2? +

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

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

sap_fetch_escrow_v2 is provided by the Sap MCP server (https://mcp.sap.oobeprotocol.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Sap, and thousands of servers like it.

This server

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sap's. Pull the full record:

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.