Low Risk

sap_get_popup_window

Check if a popup/modal dialog is open (wnd[1], wnd[2], etc.).

How to control sap_get_popup_window ↓

What sap_get_popup_window does on MCP SAP GUI Server

AI agents call sap_get_popup_window to retrieve information from MCP SAP GUI Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why sap_get_popup_window needs a policy

This is a pure read operation that retrieves information about the current state of SAP GUI's UI layer. It has no side effects, does not execute code, does not modify data, and does not delete anything. The lowest severity is appropriate since checking UI state poses minimal risk even if misused by an agent.

From the tool's definition The tool 'sap_get_popup_window' is described as checking if a popup/modal dialog is open. The word 'check' indicates a query or retrieval operation with no side effects.

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

How to control sap_get_popup_window

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_get_popup_window:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "sap_get_popup_window": {}
  }
}

sap_get_popup_window is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about sap_get_popup_window

What does the sap_get_popup_window tool do? +

Check if a popup/modal dialog is open (wnd[1], wnd[2], etc.). It is categorised as a Read tool in the MCP SAP GUI Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sap_get_popup_window? +

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

sap_get_popup_window is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sap_get_popup_window? +

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

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

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

Free to start. No card required.

57 MCP SAP GUI Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.