openbook_placeOrder
Place an order on an Openbook market. 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...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/openbook-placeorder.md
What openbook_placeOrder does on Sap
AI agents use openbook_placeOrder 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 |
|---|---|---|---|
side | string | Yes | Side parameter for Openbook Place Order. |
size | string | Yes | Raw token amount (smallest unit) |
price | number | Yes | Price parameter for Openbook Place Order. |
wallet | string | Yes | Solana public key (base58) |
marketId | string | Yes | Solana public key (base58) |
orderType | string | — | Order Type parameter for Openbook Place Order. |
Parameters from the server's own tool schema.
Why openbook_placeOrder is rated Critical
Places market orders on a decentralized exchange, directly committing financial obligations.
From the tool's definition Place an order on an Openbook market
Attacks that exploit this kind of access
The rule that runs openbook_placeOrder 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 openbook_placeOrder, this is the rule to start with:
Any call to openbook_placeOrder is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every openbook_placeOrder call is checked against it from then on.
Questions about openbook_placeOrder
Place an order on an Openbook market. 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: 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 Financial tool in the Sap MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
openbook_placeOrder accepts 6 parameters: side, size, price, wallet, marketId, orderType. Required: side, size, price, wallet, marketId. The full parameter table on this page comes from the server's own tool schema.
Register the Sap MCP server in PolicyLayer and add a rule for openbook_placeOrder: 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.
openbook_placeOrder is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the openbook_placeOrder 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.
Set action: deny in the PolicyLayer policy for openbook_placeOrder. 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.
openbook_placeOrder 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.
More on Sap, and thousands of servers like it.
Across the catalogue