Click at specific coordinates and return a screenshot of the resulting screen
AI agents invoke sap_click 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.
Clicking in SAP GUI can trigger arbitrary business operations (posting documents, confirming transactions, deleting records, approving workflows). The effect is entirely context-dependent and potentially irreversible, making this an Execute-class tool with high severity due to the broad blast radius in an ERP system.
From the tool's definition 'Click at specific coordinates' — triggers UI interactions in SAP GUI, which can initiate transactions, confirm dialogs, submit forms, or activate any SAP function depending on what is clicked
Attacks that exploit this kind of access
Click at specific coordinates 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.
Register the MCP SAP GUI Server MCP server in PolicyLayer and add a rule for sap_click: 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.
sap_click 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_click 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_click. 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_click 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →