sap_move_mouse · MCP SAP GUI Server MCP: Risk & Policy

WHAT IT DOES

What sap_move_mouse does on MCP SAP GUI Server

AI agents invoke sap_move_mouse 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 sap_move_mouse needs a policy

Moving the mouse in a live SAP GUI session is an external operation with context-dependent effects. While mouse movement alone is less dangerous than a click, in the context of a server that 'allows precise control of SAP transactions,' positioning the cursor can precede or be combined with other actions. It is categorized as Execute because it triggers an external GUI operation.

From the tool's definition 'Move mouse cursor to specific coordinates' — triggers a GUI interaction (mouse movement) within SAP GUI, an external application whose effects depend on the target coordinates and current SAP screen state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

sap_move_mouse Rate-limited

sap_move_mouse 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": {
    "sap_move_mouse": {
      "limits": [
        {
          "counter": "sap_move_mouse_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 sap_move_mouse

What does the sap_move_mouse tool do? +

Move mouse cursor to specific coordinates and return a screenshot of the 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 sap_move_mouse? +

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

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

Can I rate-limit sap_move_mouse? +

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

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

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