adt_unlock

THE RISK

Medium Risk

Why adt_unlock needs a policy

Unlocking an acquired lock is a Write operation—it modifies system state (lock status) reversibly. It's not a Read (no data retrieval), not Execute (no code execution), not Destructive (fully reversible), and not Financial. Severity is medium because improper lock release could disrupt concurrent development workflows or temporarily prevent others from acquiring needed locks, but effects are recoverable.

From the tool's definition The tool 'adt_unlock' releases a lock previously acquired with adt_lock. This modifies state in the SAP system by changing lock ownership/availability, which is a reversible state change.

Documented attack patterns abuse exactly the kind of access adt_unlock gives an agent:

POLICY

How to control adt_unlock

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_unlock:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adt_unlock": {
      "limits": [
        {
          "counter": "adt_unlock_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

adt_unlock 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.

Create a free account and register Claude For Abap — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Claude For Abap tools

Destructive adt_delete_object Delete an ABAP object. Acquires a lock and issues DELETE. Refused under read-only mode. Execute adt_pretty_print Run the ABAP pretty printer on supplied source code (stateless — no object lookup, no lock Execute adt_run_atc Run ABAP Test Cockpit (ATC) on one or more objects. ATC endpoint shape varies across NetWe Execute adt_run_atc_package Run ABAP Test Cockpit (ATC) over an ENTIRE package via the full ADT worklist flow (create Execute adt_run_atc_transport Run ABAP Test Cockpit (ATC) over every object in a transport request via the full ADT work Execute adt_run_unit_tests Run ABAP Unit tests for one or more objects (typically test container classes). Execute adt_release_transport Release a transport request. Subject to read-only mode. Execute adt_request Generic ADT REST call — escape hatch for endpoints not covered by a high-level tool. Handl

All 45 Claude For Abap tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about adt_unlock

What does the adt_unlock tool do? +

Release a stateful lock previously acquired with adt_lock. 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.

How do I enforce a policy on adt_unlock? +

Register the Claude For Abap MCP server in PolicyLayer and add a rule for adt_unlock: 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.

What risk level is adt_unlock? +

adt_unlock is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit adt_unlock? +

Yes. Add a rate_limit block to the adt_unlock 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.

How do I block adt_unlock completely? +

Set action: deny in the PolicyLayer policy for adt_unlock. 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.

What MCP server provides adt_unlock? +

adt_unlock 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.

Enforce policy on every Claude For Abap tool call.

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.

CHECK YOUR STACK →