sap_strategy_save
Free local tool. Saves or updates a strategy JSON in ~/.config/mcp-sap/strategies/. Strategies persist agent learnings (e.g. buyback rules, slippage thresholds, risk limits) across sessions. No x402 charge. SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: free; call directly wi...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-strategy-save.md
What sap_strategy_save does on Sap
AI agents use sap_strategy_save 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 |
|---|---|---|---|
name | string | Yes | Strategy name (e.g. "volatility-breakout"). |
config | string | Yes | JSON strategy configuration. |
activate | boolean | — | Whether to activate the strategy immediately. Default true. |
category | string | Yes | Strategy category (defi, trading, meme, payments, premium). |
Parameters from the server's own tool schema.
Why sap_strategy_save is rated Medium
Modifies local configuration that controls agent financial behavior (buyback rules, slippage, risk limits) across sessions.
From the tool's definition Saves or updates strategy JSON in ~/.config/mcp-sap/strategies/. Strategies persist agent learnings.
Attacks that exploit this kind of access
The rule that runs sap_strategy_save 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_strategy_save, this is the rule to start with:
sap_strategy_save 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_strategy_save call is checked against it from then on.
Questions about sap_strategy_save
Free local tool. Saves or updates a strategy JSON in ~/.config/mcp-sap/strategies/. Strategies persist agent learnings (e.g. buyback rules, slippage thresholds, risk limits) across sessions. No x402 charge. 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_strategy_save accepts 4 parameters: name, config, activate, category. Required: name, config, category. 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_strategy_save: 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_strategy_save 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_strategy_save 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_strategy_save. 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_strategy_save 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