New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

openbook_createMarket

Create a new Openbook DEX market for a token pair. 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-ch...

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp
Critical RISK CLASS
Category Financial
Parameters 55 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/openbook-createmarket.md

What openbook_createMarket does on Sap

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

ParameterTypeRequiredDescription
creator string Yes Solana public key (base58)
lotSize number Yes Minimum order size
baseMint string Yes Token mint address (base58)
tickSize number Yes Minimum price increment
quoteMint string Yes Token mint address (base58)

Parameters from the server's own tool schema.

Why openbook_createMarket is rated Critical

Creates a live DEX market, committing on-chain financial infrastructure with real economic consequences.

From the tool's definition Create a new Openbook DEX market for a token pair

Questions about openbook_createMarket

What does the openbook_createMarket tool do? +

Create a new Openbook DEX market for a token pair. 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.

What parameters does openbook_createMarket accept? +

openbook_createMarket accepts 5 parameters: creator, lotSize, baseMint, tickSize, quoteMint. Required: creator, lotSize, baseMint, tickSize, quoteMint. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on openbook_createMarket? +

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

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

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

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

openbook_createMarket 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sap's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.