adt_where_used

THE RISK

Low Risk

Why adt_where_used needs a policy

The tool performs a pure read operation—it searches for and returns references to a specified ABAP object. This is a standard static analysis query with no side effects. No data is created, modified, deleted, or executed. The blast radius if misused is minimal: an attacker could discover code dependencies and relationships, but cannot alter system state.

From the tool's definition Tool description states 'Where-used list for an object. Returns the references that point to it.' This is a query/lookup operation that retrieves existing reference data without modifying, deleting, or executing anything.

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

POLICY

How to control adt_where_used

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adt_where_used": {}
  }
}

adt_where_used is read-only, so it stays allowed — but 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.

CAP 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 →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about adt_where_used

What does the adt_where_used tool do? +

Where-used list for an object. Returns the references that point to it. It is categorised as a Read tool in the Claude For Abap MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adt_where_used? +

Register the Claude For Abap MCP server in PolicyLayer and add a rule for adt_where_used: 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_where_used? +

adt_where_used is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit adt_where_used? +

Yes. Add a rate_limit block to the adt_where_used 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_where_used completely? +

Set action: deny in the PolicyLayer policy for adt_where_used. 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_where_used? +

adt_where_used 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 →