Low Risk

test_table_access

Test if a table is accessible and return basic information

How to control test_table_access ↓

What test_table_access does on SAP RFC MCP Server

AI agents call test_table_access 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.

Low Risk

Why test_table_access needs a policy

The tool performs a test query to check table accessibility and retrieve basic information—purely informational operations with no side effects, data modification, execution of arbitrary code, deletion, or financial implications. This falls squarely into the Read category.

From the tool's definition Tool name 'test_table_access' and description 'Test if a table is accessible and return basic information' indicate read-only operations that query accessibility and retrieve metadata without modifying data.

Documented attack patterns abuse exactly the kind of access test_table_access gives an agent:

How to control test_table_access

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 test_table_access:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_table_access": {}
  }
}

test_table_access is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register SAP RFC MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about test_table_access

What does the test_table_access tool do? +

Test if a table is accessible and return basic information. It is categorised as a Read tool in the SAP RFC MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on test_table_access? +

Register the SAP RFC MCP Server MCP server in PolicyLayer and add a rule for test_table_access: 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.

What risk level is test_table_access? +

test_table_access is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit test_table_access? +

Yes. Add a rate_limit block to the test_table_access 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.

How do I block test_table_access completely? +

Set action: deny in the PolicyLayer policy for test_table_access. 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.

What MCP server provides test_table_access? +

test_table_access 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.

Enforce policy on every SAP RFC MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.