sap_prepare_action
Free intent-level preflight planner for SAP MCP. Call before paid calls, swaps, registry writes, escrow, identity updates, external x402 calls, premium streams, or transaction finalization. It returns the correct hosted/local route, fresh-data requirements, max-price guidance, confirmation policy...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-prepare-action.md
What sap_prepare_action does on Sap
AI agents call sap_prepare_action to retrieve information from Sap without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
intent | string | — | Closest user intent. Use registry-write for agent registration, update-agent for profile/image updates, swap for token swaps, escrow for SAP Escrow V2, external |
toolName | string | — | Exact hosted or local tool name being planned, such as jupiter_getOrder, sap_update_agent, sap_create_escrow_v2, or sap_payments_register_agent. |
userGoal | string | — | Short user-facing goal in natural language, used only to tailor the plan and proof-tape shape. |
maxPriceUsd | number | — | Optional user or policy x402 spend cap for this planned action. Agents should normally estimate first and use estimate × 1.25. |
estimatedNotionalUsd | number | — | Optional estimated trade, escrow, or value-moving notional in USD for confirmation-policy guidance. |
hasSubmittedSignature | boolean | — | Set true when a transaction signature was already submitted. The planner will route to verification before any retry. |
hasUnsignedTransaction | boolean | — | Set true when a hosted builder already returned unsigned transaction bytes that should be finalized locally. |
Parameters from the server's own tool schema.
Why sap_prepare_action is rated Low
Read-only planner that returns routing and policy guidance without executing any actions.
From the tool's definition preflight planner... without charging x402... returns correct route, guidance
Attacks that exploit this kind of access
The rule that runs sap_prepare_action 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_action, this is the rule to start with:
sap_prepare_action is read-only, so it stays allowed. 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_action call is checked against it from then on.
Questions about sap_prepare_action
Free intent-level preflight planner for SAP MCP. Call before paid calls, swaps, registry writes, escrow, identity updates, external x402 calls, premium streams, or transaction finalization. It returns the correct hosted/local route, fresh-data requirements, max-price guidance, confirmation policy, retry rules, proof-tape shape, and forbidden actions without charging x402. 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 Read tool in the Sap MCP Server, which means it retrieves data without modifying state.
sap_prepare_action accepts 7 parameters: intent, toolName, userGoal, maxPriceUsd, estimatedNotionalUsd, hasSubmittedSignature, hasUnsignedTransaction. 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_action: 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_action is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sap_prepare_action 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_action. 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_action 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