save
A write tool on the Sap Btp Destination MCP server.
This record as markdown: /tools/facusada-mcp-btp/save.md
What save does on Sap Btp Destination
AI agents use save to create or update resources in Sap Btp Destination, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sap Btp Destination environment.
Why save is rated Medium
The 'save' operation typically creates or modifies data reversibly within a system. In the SAP BTP Destination context, this likely persists configuration changes. While potentially serious given the authentication/credential scope, without explicit evidence of destructive behavior (delete/drop) or financial impact, Write is appropriate. Confidence is moderate due to the empty description, which limits certainty.
From the tool's definition Tool name 'save' on an SAP BTP Destination server implies persisting or modifying destination configurations, credentials, or related data. No explicit description provided; classification inferred from context and naming convention.
Attacks that exploit this kind of access
The rule that runs save safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sap Btp Destination, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save, this is the rule to start with:
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 Btp Destination, apply this rule, and every save call is checked against it from then on.
Questions about save
save is a write tool on the Sap Btp Destination MCP server. It is categorised as a Write tool in the Sap Btp Destination MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sap Btp Destination MCP server in PolicyLayer and add a rule for 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 Btp Destination. Nothing to install.
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 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 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.
save is provided by the Sap Btp Destination MCP server (facusada/mcp-btp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sap Btp Destination, and thousands of servers like it.
This server
Across the catalogue