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

manifest_cancelOrder

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

SERVERSap SOURCEhttps://mcp.sap.oobeprotocol.ai/mcp
Critical RISK CLASS
Category Destructive
Parameters 33 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/manifest-cancelorder.md

What manifest_cancelOrder does on Sap

AI agents call manifest_cancelOrder to permanently remove resources in Sap, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
wallet string Yes Solana public key (base58)
orderId string Yes Order ID parameter for Manifest Cancel Order.
marketId string Yes Solana public key (base58)

Parameters from the server's own tool schema.

Why manifest_cancelOrder is rated Critical

An AI agent that decides to call manifest_cancelOrder doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Sap is gone. There is no undo for destructive operations.

Questions about manifest_cancelOrder

What does the manifest_cancelOrder tool do? +

Cancel 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 Destructive tool in the Sap MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does manifest_cancelOrder accept? +

manifest_cancelOrder accepts 3 parameters: wallet, orderId, marketId. Required: wallet, orderId, marketId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on manifest_cancelOrder? +

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

manifest_cancelOrder is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit manifest_cancelOrder? +

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

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

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