Stream large table data from RFC functions in chunks
AI agents call stream_rfc_table_data to retrieve information from SAP RFC MCP 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 streams table data from SAP systems without modifying, executing code, or deleting data. However, severity is elevated to 'medium' rather than 'low' because: (1) SAP systems often contain sensitive business-critical data (financial records, customer information, supply chain data), (2) streaming large volumes of data could enable exfiltration attacks, (3) the tool operates on 'RFC functions'…
From the tool's definition Tool name 'stream_rfc_table_data' and description 'Stream large table data from RFC functions in chunks' indicates data retrieval operation.
Documented attack patterns abuse exactly the kind of access stream_rfc_table_data gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SAP RFC MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stream_rfc_table_data:
{
"version": "1",
"default": "deny",
"tools": {
"stream_rfc_table_data": {}
}
} stream_rfc_table_data 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.
Stream large table data from RFC functions in chunks. It is categorised as a Read tool in the SAP RFC MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SAP RFC MCP Server MCP server in PolicyLayer and add a rule for stream_rfc_table_data: 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 SAP RFC MCP Server. Nothing to install.
stream_rfc_table_data 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 stream_rfc_table_data 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 stream_rfc_table_data. 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.
stream_rfc_table_data is provided by the SAP RFC MCP Server MCP server (thupalo/sap-rfc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SAP RFC MCP 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.
15 SAP RFC MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.