sap_phoenix_submit_onboard_trader

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

Medium RISK CLASS

Category Write

Parameters 33 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-submit-onboard-trader.md

WHAT IT DOES

What sap_phoenix_submit_onboard_trader does on Sap

AI agents use sap_phoenix_submit_onboard_trader to create or update resources in Sap, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sap environment.

Parameter	Type	Required	Description
`txFeePayer`	string	Yes	Fee payer wallet public key (base58) — same as used in build_onboard_trader.
`transaction`	string	Yes	Base64-encoded transaction assembled from build_onboard_trader instructions and signed by the fee payer.
`traderAuthority`	string	Yes	Trader authority wallet public key (base58) — same as used in build_onboard_trader.

Parameters from the server's own tool schema.

RISK

Why sap_phoenix_submit_onboard_trader is rated Medium

An AI agent can call sap_phoenix_submit_onboard_trader faster than any human can review: one bad instruction and it creates or modifies resources in Sap by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

sap_phoenix_submit_onboard_trader Rate-limited

sap_phoenix_submit_onboard_trader stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_submit_onboard_trader": {
      "limits": [
        {
          "counter": "sap_phoenix_submit_onboard_trader_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_submit_onboard_trader call is checked against it from then on.

FAQ

Questions about sap_phoenix_submit_onboard_trader

What does the sap_phoenix_submit_onboard_trader tool do? +

Submit a user-signed Phoenix activation transaction through Phoenix's co-signing API (send-register-ixs): Phoenix validates it, adds the onboarder signature, simulates, verifies the onboarder pays nothing, and broadcasts. Pair with sap_phoenix_build_onboard_trader. After success verify with sap_phoenix_get_trader_state (state leaves "frozen", depositCollateral.immediate=true) before building deposits. SAP MCP execution guidance: Intent: Solana value-action or trading workflow. 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 Write tool in the Sap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does sap_phoenix_submit_onboard_trader accept? +

sap_phoenix_submit_onboard_trader accepts 3 parameters: txFeePayer, transaction, traderAuthority. Required: txFeePayer, transaction, 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_submit_onboard_trader? +

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

sap_phoenix_submit_onboard_trader is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sap_phoenix_submit_onboard_trader? +

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

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

sap_phoenix_submit_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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →