sap_phoenix_get_deposit_status
Check the status of a cross-chain deposit via Relay.link. Returns the current status (pending/success/failed/refunded), transaction hashes, and chain IDs. Use the requestId from sap_phoenix_get_cross_chain_quote. Free read. SAP MCP execution guidance: Intent: read/discovery workflow. Pricing: pai...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-phoenix-get-deposit-status.md
What sap_phoenix_get_deposit_status does on Sap
AI agents call sap_phoenix_get_deposit_status 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
requestId | string | Yes | Request ID from the cross-chain quote response. Required. |
Parameters from the server's own tool schema.
Why sap_phoenix_get_deposit_status is rated Low
Tool queries deposit status without modifying state or triggering financial transfers.
From the tool's definition Check status of cross-chain deposit. Returns current status, transaction hashes, chain IDs. Free read.
Attacks that exploit this kind of access
The rule that runs sap_phoenix_get_deposit_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sap, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sap_phoenix_get_deposit_status, this is the rule to start with:
sap_phoenix_get_deposit_status 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 Sap, apply this rule, and every sap_phoenix_get_deposit_status call is checked against it from then on.
Questions about sap_phoenix_get_deposit_status
Check the status of a cross-chain deposit via Relay.link. Returns the current status (pending/success/failed/refunded), transaction hashes, and chain IDs. Use the requestId from sap_phoenix_get_cross_chain_quote. Free read. 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.
sap_phoenix_get_deposit_status accepts 1 parameter: requestId. Required: requestId. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for sap_phoenix_get_deposit_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 Sap. Nothing to install.
sap_phoenix_get_deposit_status 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 sap_phoenix_get_deposit_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.
Set action: deny in the PolicyLayer policy for sap_phoenix_get_deposit_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.
sap_phoenix_get_deposit_status 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