List runtime enqueue locks (the SM12 analog). NOTE: most ABAP systems do NOT expose SM12 runtime enqueues over ADT REST — in that case the response carries available:false and a hint to use SM12. This is distinct from the editing lock acquired by adt_lock (a single object) and from DDIC lock-obje...
AI agents call adt_list_locks 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.
adt_list_locks retrieves and displays lock status from the SAP system without creating, modifying, or deleting any data. It is purely observational, analogous to viewing SM12 in the SAP GUI. The tool has minimal blast radius—misuse would only expose lock information, not alter system state. This is a straightforward Read category tool.
From the tool's definition Tool description states 'List runtime enqueue locks' — a query/retrieval operation with no modification. The note that 'most ABAP systems do NOT expose SM12 runtime enqueues over ADT REST' and returns 'available:false' further confirms this is a read-only…
Documented attack patterns abuse exactly the kind of access adt_list_locks 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_list_locks:
{
"version": "1",
"default": "deny",
"tools": {
"adt_list_locks": {}
}
}adt_list_locks 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.
List runtime enqueue locks (the SM12 analog). NOTE: most ABAP systems do NOT expose SM12 runtime enqueues over ADT REST — in that case the response carries available:false and a hint to use SM12. This is distinct from the editing lock acquired by adt_lock (a single object) and from DDIC lock-object definitions. 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_list_locks: 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_list_locks 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_list_locks 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_list_locks. 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_list_locks 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.