sap_profile_switch
Switch the live SAP MCP runtime to another existing profile and reload client, signer, connection, and policy. 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. ...
This record as markdown: /tools/oobe-protocol-labs-sap-mcp-server/sap-profile-switch.md
What sap_profile_switch does on Sap
AI agents invoke sap_profile_switch to trigger actions in Sap. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
confirm | boolean | — | Must be true because switching profile can change signer, network, and policy. |
signature | string | — | Optional Ed25519 signature proving ownership of the target profile keypair. When provided, the server verifies that the signature matches the profile agentPubke |
profileName | string | — | Existing profile name to load. |
Parameters from the server's own tool schema.
Why sap_profile_switch is rated High
Switching runtime profiles reloads critical security components including signer and policy configurations.
From the tool's definition Switch live SAP MCP runtime, reload client, signer, connection, and policy
Attacks that exploit this kind of access
The rule that runs sap_profile_switch 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_profile_switch, this is the rule to start with:
sap_profile_switch stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_profile_switch call is checked against it from then on.
Questions about sap_profile_switch
Switch the live SAP MCP runtime to another existing profile and reload client, signer, connection, and policy. 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: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. 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 Execute tool in the Sap MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
sap_profile_switch accepts 3 parameters: confirm, signature, profileName. 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_profile_switch: 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_profile_switch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sap_profile_switch 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_profile_switch. 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_profile_switch 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