sap_connect_existing

THE RISK

High Risk

Why sap_connect_existing needs a policy

This tool establishes a connection to an existing SAP GUI session. While it doesn't directly read/write/delete data, it initiates a session attachment that enables subsequent operations within SAP — an external system interaction that depends on runtime state.

From the tool's definition Connect to an already open SAP session. Use this when SAP is already logged in.

Documented attack patterns abuse exactly the kind of access sap_connect_existing gives an agent:

POLICY

How to control sap_connect_existing

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP SAP GUI Server, and nothing reaches the server without passing your rules. This is the rule we recommend for sap_connect_existing:

policy.json

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

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

Create a free account and register MCP SAP GUI Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP SAP GUI Server tools

Execute sap_execute_transaction sap_execute_transaction Execute sap_click_tree_link Click a hyperlink in a tree node item. Execute sap_collapse_tree_node Collapse a folder node in a tree control Execute sap_connect sap_connect Execute sap_disconnect Disconnect from the current SAP session and release the binding. Execute sap_double_click_cell Double-click a cell in a table/grid (often opens details or drills down). Execute sap_double_click_tree_item Double-click a specific item (column cell) in a tree node row. Execute sap_double_click_tree_node Double-click a node in a tree control (often opens details or drills down).

All 57 MCP SAP GUI Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in MCP SAP GUI Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about sap_connect_existing

What does the sap_connect_existing tool do? +

Connect to an already open SAP session. Use this when SAP is already logged in. 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 sap_connect_existing? +

Register the MCP SAP GUI Server MCP server in PolicyLayer and add a rule for sap_connect_existing: 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 sap_connect_existing? +

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

Can I rate-limit sap_connect_existing? +

Yes. Add a rate_limit block to the sap_connect_existing 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 sap_connect_existing completely? +

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

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

Enforce policy on every MCP SAP GUI Server tool call.

Start from MCP SAP GUI Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →