launch_transaction · MCP SAP GUI Server MCP: Risk & Policy

WHAT IT DOES

What launch_transaction does on MCP SAP GUI Server

AI agents invoke launch_transaction to trigger actions in MCP SAP GUI Server. 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.

WHY IT NEEDS A POLICY

Why launch_transaction needs a policy

This tool executes external operations (SAP transactions) whose effects depend on user-supplied arguments (the transaction code). While not destructive by itself, it can trigger any SAP transaction including financial, data modification, or system-level operations. The Execute category is most appropriate because the actual impact depends on which transaction is launched.

From the tool's definition 'Launch SAP transaction code' indicates execution of SAP transaction logic with side effects determined by the transaction code argument.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

launch_transaction Rate-limited

launch_transaction 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "launch_transaction": {
      "limits": [
        {
          "counter": "launch_transaction_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP SAP GUI Server, so you can run agents against it safely.

FAQ

Questions about launch_transaction

What does the launch_transaction tool do? +

Launch SAP transaction code and return a screenshot of the resulting screen. It is categorised as a Execute tool in the MCP SAP GUI Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on launch_transaction? +

Register the MCP SAP GUI Server MCP server in PolicyLayer and add a rule for launch_transaction: 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 MCP SAP GUI Server. Nothing to install.

What risk level is launch_transaction? +

launch_transaction is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit launch_transaction? +

Yes. Add a rate_limit block to the launch_transaction 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.

How do I block launch_transaction completely? +

Set action: deny in the PolicyLayer policy for launch_transaction. 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.

What MCP server provides launch_transaction? +

launch_transaction is provided by the MCP SAP GUI Server MCP server (mario-andreschak/mcp-sap-gui). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.