Report the implementation status of a SAP Note in the system (e.g. can be implemented / obsolete / fully implemented / partially implemented). EXPERIMENTAL — see adt_get_note for availability constraints.
AI agents call adt_check_note_status 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 retrieves and reports information about SAP Note implementation status in the system. It has no side effects, does not create, modify, or delete data, and does not execute commands or trigger external operations. It is a pure information retrieval operation, making it a Read category tool with low severity since misuse would only expose system configuration information about applied patches/notes.
From the tool's definition Tool name and description indicate it 'Report[s] the implementation status of a SAP Note' — a query operation that checks status without modifying, deleting, or executing code. The verb 'report' and 'status' checking are characteristic of Read operations.
Documented attack patterns abuse exactly the kind of access adt_check_note_status 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_check_note_status:
{
"version": "1",
"default": "deny",
"tools": {
"adt_check_note_status": {}
}
} adt_check_note_status 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.
Report the implementation status of a SAP Note in the system (e.g. can be implemented / obsolete / fully implemented / partially implemented). EXPERIMENTAL — see adt_get_note for availability constraints. 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_check_note_status: 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_check_note_status 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_check_note_status 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_check_note_status. 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_check_note_status 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.