Diff every object listed in a transport between two systems. Capped at maxObjects (default 50).
AI agents call adt_transport_diff 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.
The adt_transport_diff tool retrieves and compares object metadata from a transport across systems. It does not create, modify, delete, or execute any ABAP code or trigger external operations. The capping mechanism (maxObjects default 50) further indicates this is a bounded read query. Diffing is a classic read operation with no side effects.
From the tool's definition Tool description states it performs a diff operation on transport objects 'between two systems' — a comparison/retrieval of differences with no modification, deletion, or execution of code.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access adt_transport_diff 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_transport_diff:
{
"version": "1",
"default": "deny",
"tools": {
"adt_transport_diff": {}
}
} adt_transport_diff 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.
Diff every object listed in a transport between two systems. Capped at maxObjects (default 50). 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_transport_diff: 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_transport_diff 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_transport_diff 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_transport_diff. 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_transport_diff 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.