bridging_bridgeWormholeStatus

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp

Low RISK CLASS

Category Read

Parameters 22 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/bridging-bridgewormholestatus.md

WHAT IT DOES

What bridging_bridgeWormholeStatus does on Sap

AI agents call bridging_bridgeWormholeStatus 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
`sequence`	string	Yes	Wormhole sequence number from bridgeWormhole response
`sourceChain`	string	Yes	Source Chain parameter for Bridging Bridge Wormhole Status.

Parameters from the server's own tool schema.

RISK

Why bridging_bridgeWormholeStatus is rated Low

Queries bridge transfer status without modifying data or triggering financial transactions.

From the tool's definition Check status of Wormhole bridge transfer; read operation; no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bridging_bridgeWormholeStatus 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 bridging_bridgeWormholeStatus, this is the rule to start with:

bridging_bridgeWormholeStatus Allowed

bridging_bridgeWormholeStatus 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": {
    "bridging_bridgeWormholeStatus": {}
  }
}

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

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

FAQ

Questions about bridging_bridgeWormholeStatus

What does the bridging_bridgeWormholeStatus tool do? +

Check the status of a Wormhole bridge transfer. SAP MCP context: Protocol bridging; operation class read. Use to check Wormhole bridge transfer status after a bridge submission. Call this after bridging_bridgeWormhole and keep the resulting status with the user-facing bridge audit trail. SAP MCP execution guidance: Intent: SAP MCP tool 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 bridging_bridgeWormholeStatus accept? +

bridging_bridgeWormholeStatus accepts 2 parameters: sequence, sourceChain. Required: sequence, sourceChain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on bridging_bridgeWormholeStatus? +

Register the Sap MCP server in PolicyLayer and add a rule for bridging_bridgeWormholeStatus: 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 bridging_bridgeWormholeStatus? +

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

Can I rate-limit bridging_bridgeWormholeStatus? +

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

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

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

KEEP EXPLORING

More on Sap, and thousands of servers like it.

This server

All 375 Sap tools →

Across the catalogue

The MCP Attack Database →

Guides

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