sap_phoenix_build_onboard_trader

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

High RISK CLASS

Category Execute

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-phoenix-build-onboard-trader.md

WHAT IT DOES

What sap_phoenix_build_onboard_trader does on Sap

AI agents invoke sap_phoenix_build_onboard_trader to trigger actions in Sap. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`txFeePayer`	string	Yes	Wallet paying fees and rent (base58). Usually the same as traderAuthority. Must NOT be the Phoenix onboarder.
`maxPositions`	number	—	Max positions for registration (32-128, default 128). Only used when the account still needs RegisterTrader.
`traderAuthority`	string	Yes	Trader authority wallet public key (base58, FULL 44 chars).

Parameters from the server's own tool schema.

RISK

Why sap_phoenix_build_onboard_trader is rated High

Assembles and signs blockchain transactions for trader account activation with deposit permissions; effects depend on submission arguments.

From the tool's definition Build Phoenix trader activation instructions, assembles and signs transactions, deposit capability.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_phoenix_build_onboard_trader Rate-limited

sap_phoenix_build_onboard_trader stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sap_phoenix_build_onboard_trader": {
      "limits": [
        {
          "counter": "sap_phoenix_build_onboard_trader_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about sap_phoenix_build_onboard_trader

What does the sap_phoenix_build_onboard_trader tool do? +

Build Phoenix trader ACTIVATION instructions (enables all six capabilities incl. deposit). ALWAYS required after register — a RegisterTrader-only account is frozen and every deposit simulates CapabilityDenied. Fetches instructions from Phoenix's build-register-ixs API (the only source of the OnboardTraderDelegated instruction). The browser assembles and signs them, then MUST submit via sap_phoenix_submit_onboard_trader — never via plain RPC, the onboarder signature exists only inside Phoenix's send-register-ixs. SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. 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 Execute tool in the Sap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does sap_phoenix_build_onboard_trader accept? +

sap_phoenix_build_onboard_trader accepts 3 parameters: txFeePayer, maxPositions, traderAuthority. Required: txFeePayer, traderAuthority. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on sap_phoenix_build_onboard_trader? +

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

sap_phoenix_build_onboard_trader is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit sap_phoenix_build_onboard_trader? +

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

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

sap_phoenix_build_onboard_trader 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 453 Sap tools → High-risk tools on this server →

Across the catalogue

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

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →