Read table with all requested fields using iterative method to avoid buffer overflow
AI agents call read_table_complete 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 data from SAP tables without modifying, deleting, or executing code. The iterative method mentioned is a technical implementation detail to handle large datasets safely, not an indicator of side effects. It fits the Read category: retrieves data with no side effects.
From the tool's definition Tool name is 'read_table_complete' and description states 'Read table with all requested fields using iterative method' - the verb 'Read' and the focus on retrieving table data without modification indicate a data retrieval operation.
Documented attack patterns abuse exactly the kind of access read_table_complete 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 read_table_complete:
{
"version": "1",
"default": "deny",
"tools": {
"read_table_complete": {}
}
} read_table_complete 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.
Read table with all requested fields using iterative method to avoid buffer overflow. 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 read_table_complete: 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.
read_table_complete 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 read_table_complete 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 read_table_complete. 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.
read_table_complete 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.