Ping a configured SAP system by calling the ADT discovery endpoint. Use to verify credentials and network reachability.
AI agents call adt_ping to retrieve information from Claude For Abap without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a network diagnostic check (ping) against a configured endpoint. It has no side effects, does not retrieve data beyond what is necessary for the ping response, does not modify any state, and does not execute arbitrary operations. It is purely informational/Read category.
From the tool's definition Tool description states it 'Ping a configured SAP system by calling the ADT discovery endpoint' to 'verify credentials and network reachability.' Pinging is a diagnostic/verification operation that queries system status without retrieving, modifying, or…
Documented attack patterns abuse exactly the kind of access adt_ping gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude For Abap, and nothing reaches the server without passing your rules. This is the rule we recommend for adt_ping:
{
"version": "1",
"default": "deny",
"tools": {
"adt_ping": {}
}
} adt_ping 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.
Ping a configured SAP system by calling the ADT discovery endpoint. Use to verify credentials and network reachability. It is categorised as a Read tool in the Claude For Abap MCP Server, which means it retrieves data without modifying state.
Register the Claude For Abap MCP server in PolicyLayer and add a rule for adt_ping: 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 Claude For Abap. Nothing to install.
adt_ping 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 adt_ping 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 adt_ping. 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.
adt_ping is provided by the Claude For Abap MCP server (yzonur/claude-for-abap). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude For Abap, 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.
45 Claude For Abap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.