pump_trade

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

Critical RISK CLASS

Category Financial

Parameters 54 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/pump-trade.md

WHAT IT DOES

What pump_trade does on Sap

AI agents use pump_trade 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
`mint`	string	Yes	Pump.fun token mint
`action`	string	Yes	Trade direction
`amount`	string	Yes	Amount in SOL (buy) or tokens (sell)
`wallet`	string	Yes	Solana public key (base58)
`slippageBps`	number	—	Slippage Bps pagination control for Pump Trade.

Parameters from the server's own tool schema.

RISK

Why pump_trade is rated Critical

Directly executes token trades involving real financial value on Solana blockchain.

From the tool's definition Buy or sell tokens on Pump.fun bonding curve

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pump_trade Approval-gated

Any call to pump_trade 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": {
    "pump_trade": {
      "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 pump_trade call is checked against it from then on.

FAQ

Questions about pump_trade

What does the pump_trade tool do? +

Buy or sell tokens on Pump.fun bonding curve. SAP MCP context: This Synapse AgentKit tool is served beside the sap_* SDK tools. Use sap_agent_identity_plan, sap_payments_register_agent, sap_payments_update_agent, and sap_publish_tool_by_name when the capability should become part of an on-chain SAP agent profile or tool registry entry. SAP MCP execution guidance: Intent: Solana value-action or trading 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 pump_trade accept? +

pump_trade accepts 5 parameters: mint, action, amount, wallet, slippageBps. Required: mint, action, amount, wallet. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on pump_trade? +

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

pump_trade 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 pump_trade? +

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

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

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