Set a value in a field on the current SAP screen.
AI agents use sap_set_field to create or update resources in MCP SAP GUI Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP SAP GUI Server environment.
This tool modifies data in SAP fields, which is a Write operation. It is not Destructive because field modifications are typically reversible through SAP's audit trails and undo mechanisms. However, severity is high rather than medium because SAP systems handle sensitive business-critical data including financial transactions, inventory, and customer information.
From the tool's definition Tool name 'sap_set_field' and description 'Set a value in a field on the current SAP screen' indicate modification of data fields within SAP GUI.
Documented attack patterns abuse exactly the kind of access sap_set_field 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_set_field:
{
"version": "1",
"default": "deny",
"tools": {
"sap_set_field": {
"limits": [
{
"counter": "sap_set_field_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} sap_set_field stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set a value in a field on the current SAP screen. It is categorised as a Write tool in the MCP SAP GUI Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP SAP GUI Server MCP server in PolicyLayer and add a rule for sap_set_field: 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_set_field is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sap_set_field 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_set_field. 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_set_field 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.