manifest_placeLimitOrder

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

Critical RISK CLASS

Category Financial

Parameters 65 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/manifest-placelimitorder.md

WHAT IT DOES

What manifest_placeLimitOrder does on Sap

AI agents use manifest_placeLimitOrder 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 Manifest Place Limit Order.
`size`	string	Yes	Order size in base tokens
`price`	number	Yes	Limit price
`wallet`	string	Yes	Solana public key (base58)
`marketId`	string	Yes	Solana public key (base58)
`orderType`	string	—	Order Type parameter for Manifest Place Limit Order.

Parameters from the server's own tool schema.

RISK

Why manifest_placeLimitOrder is rated Critical

Places financial orders on a market, directly committing financial obligations.

From the tool's definition Place a limit order on a Manifest market

Attacks that exploit this kind of access

RECOMMENDED RULE

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

manifest_placeLimitOrder Approval-gated

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

FAQ

Questions about manifest_placeLimitOrder

What does the manifest_placeLimitOrder tool do? +

Place a limit order on a Manifest 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: 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 manifest_placeLimitOrder accept? +

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

How do I enforce a policy on manifest_placeLimitOrder? +

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

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

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

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

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