Return a generic, read-first guide for a supported SAP transaction.
AI agents call sap_get_transaction_guide 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.
This tool retrieves and returns documentation or guidance about SAP transactions. It performs a query/retrieval operation with no capability to modify, execute, or delete data. The 'read-first' qualifier explicitly indicates this is informational/educational content. No system state changes, financial impact, or irreversible actions are possible.
From the tool's definition Tool name and description: 'sap_get_transaction_guide' — 'Return a generic, read-first guide for a supported SAP transaction.' The verb 'Return' and the phrase 'read-first guide' indicate retrieval of informational content with no side effects or data…
Documented attack patterns abuse exactly the kind of access sap_get_transaction_guide 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_get_transaction_guide:
{
"version": "1",
"default": "deny",
"tools": {
"sap_get_transaction_guide": {}
}
} sap_get_transaction_guide is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Return a generic, read-first guide for a supported SAP transaction. It is categorised as a Read tool in the MCP SAP GUI Server MCP Server, which means it retrieves data without modifying state.
Register the MCP SAP GUI Server MCP server in PolicyLayer and add a rule for sap_get_transaction_guide: 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_get_transaction_guide is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sap_get_transaction_guide 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_get_transaction_guide. 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_get_transaction_guide 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.