bridging_bridgeWormhole

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

Critical RISK CLASS

Category Financial

Parameters 76 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/bridging-bridgewormhole.md

WHAT IT DOES

What bridging_bridgeWormhole does on Sap

AI agents use bridging_bridgeWormhole to commit financial operations through Sap, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Parameter	Type	Required	Description
`token`	string	Yes	Token address on source chain
`amount`	string	Yes	Amount to bridge (raw, smallest unit)
`sender`	string	Yes	Sender wallet on source chain
`recipient`	string	Yes	Recipient address on destination chain
`relayerFee`	string	—	Raw token amount (smallest unit, no decimals)
`sourceChain`	string	Yes	Source chain identifier (e.g. "solana", "ethereum", "base", "polygon")
`destinationChain`	string	Yes	Destination chain identifier

Parameters from the server's own tool schema.

RISK

Why bridging_bridgeWormhole is rated Critical

Moves crypto assets across blockchains, constituting irreversible financial transfers.

From the tool's definition Bridge tokens across chains; cross-chain asset movement

Risk signalsHandles credentials or secrets (token)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

bridging_bridgeWormhole Approval-gated

Any call to bridging_bridgeWormhole is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bridging_bridgeWormhole": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about bridging_bridgeWormhole

What does the bridging_bridgeWormhole tool do? +

Bridge tokens across chains via Wormhole. Supports Solana ↔ EVM chains. SAP MCP context: Protocol bridging; operation class write. Use for cross-chain asset movement through Wormhole or deBridge. Confirm source chain, destination chain, token mint, amount, recipient, route fees, and finality expectations before invoking a bridge write. For bridge flows call the matching status tool after submission. If the bridge capability belongs to a registered SAP agent, plan the profile with sap_agent_identity_plan, register through sap_payments_register_agent, then advertise bridge capability IDs with sap_payments_update_agent or sap_publish_tool_by_name. 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: hosted accountless write is blocked; do not call this as a paid hosted write and no x402 payment should be charged. Use the local sap_payments bridge or a hosted unsigned builder when user signing is required. Signer boundary: user-controlled local profile or external signer; OOBE hosted MCP remains non-custodial. It is categorised as a Financial tool in the Sap MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

What parameters does bridging_bridgeWormhole accept? +

bridging_bridgeWormhole accepts 7 parameters: token, amount, sender, recipient, relayerFee, sourceChain, destinationChain. Required: token, amount, sender, recipient, sourceChain, destinationChain. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on bridging_bridgeWormhole? +

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

bridging_bridgeWormhole is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit bridging_bridgeWormhole? +

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

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

bridging_bridgeWormhole 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →