Replace the ABAP source of an object. The supplied
AI agents use adt_set_source to create or update resources in Claude For Abap — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude For Abap environment.
This tool modifies existing ABAP source code in a SAP system, which is a reversible write operation (the previous version can be recovered via version control or adt_compare_versions). It does not delete data (would be Destructive) but does create production code changes in an enterprise system, making it high severity.
From the tool's definition Tool name 'adt_set_source' and description 'Replace the ABAP source of an object' indicate modification of code artifacts in a live SAP system.
Documented attack patterns abuse exactly the kind of access adt_set_source 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_set_source:
{
"version": "1",
"default": "deny",
"tools": {
"adt_set_source": {
"limits": [
{
"counter": "adt_set_source_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} adt_set_source stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Replace the ABAP source of an object. The supplied. It is categorised as a Write tool in the Claude For Abap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude For Abap MCP server in PolicyLayer and add a rule for adt_set_source: 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_set_source is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the adt_set_source 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_set_source. 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_set_source 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.