Select a radio button on the current SAP screen.
AI agents invoke sap_select_radio_button 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.
Selecting a radio button triggers a UI interaction in SAP GUI that changes the state of the current screen/form. This is an Execute action as it drives an external application (SAP GUI) through the Scripting API. While selecting a radio button alone is low-impact, within an SAP workflow it can change transaction behavior or flow, potentially leading to unintended operations.
From the tool's definition Select a radio button on the current SAP screen
Documented attack patterns abuse exactly the kind of access sap_select_radio_button gives an agent:
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_select_radio_button:
{
"version": "1",
"default": "deny",
"tools": {
"sap_select_radio_button": {
"limits": [
{
"counter": "sap_select_radio_button_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} sap_select_radio_button 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.
Free to start. No card required.
Select a radio button on the current SAP 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_select_radio_button: 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_select_radio_button 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_select_radio_button 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_select_radio_button. 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_select_radio_button 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.
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.