sap_prepare_mandate
Free AP2-style mandate planner for SAP MCP agent commerce. It converts a user intent into a bounded, unsigned planning artifact with spend limits, tool/protocol allow-lists, freshness rules, confirmation thresholds, proof-tape fields, and the correct hosted/local signing route. This tool does not...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-prepare-mandate.md
What sap_prepare_mandate does on Sap
AI agents use sap_prepare_mandate to create or update resources in Sap, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sap environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
intent | string | Yes | Human intent to bind, for example "check solking.sol", "register Solking", "swap 0.05 SOL to USDC", or "open a $10 BONK short". |
wallet | string | — | Optional expected owner/signer wallet public key in base58. Used only as a public constraint, never as a keypair path. |
profile | string | — | Optional local SAP profile name the user expects the runtime to use. Do not guess wallet/keypair paths from this value. |
maxX402Usd | number | — | Maximum x402/pay.sh fee the agent may auto-pay for one hosted tool call under the user policy. |
maxTradeUsd | number | — | Maximum value-moving notional in USD for swaps, perps, escrow, or transaction finalization under this mandate. |
allowedTools | array | — | Exact SAP MCP tool allow-list for this mandate. Use exact names from tools/list and do not rewrite hyphenated tools. |
operationType | string | — | Closest operation family. Use registry-write for SAP agent registration/update, escrow for SAP Escrow V2, and transaction-finalize when an unsigned hosted trans |
maxSlippageBps | number | — | Maximum slippage in basis points for swap or trading routes. 100 means 1%. |
maxTotalX402Usd | number | — | Maximum total x402/pay.sh spend for this mandate before asking the user again. |
allowedProtocols | array | — | Protocol allow-list such as sap, mcp, x402, jupiter, adrena, pyth, metaplex, sns, magicblock, or custom protocol ids. |
expiresInSeconds | number | — | Mandate TTL in seconds. Defaults to 900 and is capped to 86400. |
requireConfirmationAboveUsd | number | — | Require a human preview and explicit confirmation above this USD notional or spend threshold. |
Parameters from the server's own tool schema.
Why sap_prepare_mandate is rated Medium
Creates a planning artifact with spend limits and configuration; no signing or payment execution.
From the tool's definition converts user intent into bounded, unsigned planning artifact
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs sap_prepare_mandate 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 sap_prepare_mandate, this is the rule to start with:
sap_prepare_mandate stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sap, apply this rule, and every sap_prepare_mandate call is checked against it from then on.
Questions about sap_prepare_mandate
Free AP2-style mandate planner for SAP MCP agent commerce. It converts a user intent into a bounded, unsigned planning artifact with spend limits, tool/protocol allow-lists, freshness rules, confirmation thresholds, proof-tape fields, and the correct hosted/local signing route. This tool does not sign, submit, authorize payment, or replace wallet confirmation. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. 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 Write tool in the Sap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
sap_prepare_mandate accepts 12 parameters: intent, wallet, profile, maxX402Usd, maxTradeUsd, allowedTools, operationType, maxSlippageBps, maxTotalX402Usd, allowedProtocols, expiresInSeconds, requireConfirmationAboveUsd. Required: intent. 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 sap_prepare_mandate: 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.
sap_prepare_mandate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sap_prepare_mandate 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 sap_prepare_mandate. 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.
sap_prepare_mandate 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.
This server
Across the catalogue