Implement (download + apply) a SAP Note via the Note Assistant ADT API. WRITE operation — subject to read-only mode and requires a transport. EXPERIMENTAL and potentially disruptive: implementing a note changes system objects. Only available on systems shipping the SNOTE ADT plug-in. Prefer GUI S...
AI agents use adt_implement_note 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 applies SAP Notes to system objects, which modifies code and configuration reversibly but at significant scope. While technically reversible (can be undone via transport), the blast radius is high given that notes typically patch multiple objects across a system, and the 'EXPERIMENTAL' and 'potentially disruptive' warnings indicate elevated risk.
From the tool's definition Tool description explicitly states 'WRITE operation' and 'implementing a note changes system objects'. The description further warns 'EXPERIMENTAL and potentially disruptive'.
Documented attack patterns abuse exactly the kind of access adt_implement_note 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_implement_note:
{
"version": "1",
"default": "deny",
"tools": {
"adt_implement_note": {
"limits": [
{
"counter": "adt_implement_note_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} adt_implement_note 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.
Implement (download + apply) a SAP Note via the Note Assistant ADT API. WRITE operation — subject to read-only mode and requires a transport. EXPERIMENTAL and potentially disruptive: implementing a note changes system objects. Only available on systems shipping the SNOTE ADT plug-in. Prefer GUI SNOTE for anything non-trivial. 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_implement_note: 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_implement_note 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_implement_note 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_implement_note. 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_implement_note 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.