// SCAN REPORT

ABAP-ADT-API MCP-Server

127 tools. 38 can modify or destroy data without limits.

7 destructive tools with no built-in limits. Policy required.

Last updated: 20 May 2026

38 can modify or destroy data

89 read-only

127 tools total

Free to start. No card required.

TOOL MAP

Read (89) Write / Execute (31) Destructive / Financial (7)

WHAT CAN GO WRONG

Destructive tools (debuggerDeleteBreakpoints, debuggerDeleteListener, deleteObject) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (activateByName, activateObjects, createAtcRun) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (runClass, runQuery) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

RECOMMENDED RULES

Deny destructive operations

{
  "debuggerDeleteBreakpoints": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "activateByName": {
    "limits": [
      {
        "counter": "activatebyname_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "abapDocumentation": {
    "limits": [
      {
        "counter": "abapdocumentation_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

ALL 127 ABAP-ADT-API MCP-SERVER TOOLS

DESTRUCTIVE 7 tools

Destructive debuggerDeleteBreakpoints Destructive debuggerDeleteListener Destructive deleteObject Destructive dropSession Destructive tracesDelete Destructive tracesDeleteConfiguration Destructive transportDelete

EXECUTE 2 tools

Execute runClass Execute runQuery

READ 89 tools

Read abapDocumentation Read adtCompatibiliyGraph Read adtCoreDiscovery Read adtDiscovery Read annotationDefinitions Read atcChangeContact Read atcCheckVariant Read atcContactUri Read atcCustomizing Read atcExemptProposal Read atcRequestExemption Read atcUsers Read atcWorklists Read bindingDetails Read checkRepo Read classComponents Read classIncludes Read codeCompletion Read codeCompletionElement Read codeCompletionFull Read collectionFeatureDetails Read ddicElement Read ddicRepositoryAccess Read debuggerChildVariables Read debuggerGoToStack Read debuggerListen Read debuggerListeners Read debuggerStackTrace Read debuggerStep Read debuggerVariables Read dumps Read extractMethodEvaluate Read extractMethodExecute Read extractMethodPreview Read featureDetails Read feeds Read findCollectionByUrl Read findDefinition Read findObjectPath Read fixEdits Read fixProposals Read fragmentMappings Read getObjectSource Read getTransportConfiguration Read gitExternalRepoInfo Read gitPullRepo Read gitRepos Read gitUnlinkRepo Read hasTransportConfig Read healthcheck Read inactiveObjects Read isProposalMessage Read loadTypes Read logout Read mainPrograms Read nodeContents Read objectRegistrationInfo Read objectStructure Read objectTypes Read packageSearchHelp Read prettyPrinter Read prettyPrinterSetting Read reentranceTicket Read remoteRepoInfo Read revisions Read searchObject Read stageRepo Read syntaxCheckCdsUrl Read syntaxCheckCode Read syntaxCheckTypes Read systemUsers Read tableContents Read tracesDbAccess Read tracesHitList Read tracesList Read tracesListRequests Read tracesStatements Read transportConfigurations Read transportInfo Read transportReference Read transportRelease Read transportsByConfig Read unitTestEvaluation Read unitTestOccurrenceMarkers Read unitTestRun Read usageReferences Read usageReferenceSnippets Read userTransports Read validateNewObject

FAQ

Can an AI agent delete data through the ABAP-ADT-API MCP-Server MCP server? +

Yes. The ABAP-ADT-API MCP-Server server exposes 7 destructive tools including debuggerDeleteBreakpoints, debuggerDeleteListener, deleteObject. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through ABAP-ADT-API MCP-Server? +

The ABAP-ADT-API MCP-Server server has 29 write tools including activateByName, activateObjects, createAtcRun. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach ABAP-ADT-API MCP-Server.

How many tools does the ABAP-ADT-API MCP-Server MCP server expose? +

127 tools across 4 categories: Destructive, Execute, Read, Write. 89 are read-only. 38 can modify, create, or delete data.

How do I enforce a policy on ABAP-ADT-API MCP-Server? +

Register the ABAP-ADT-API MCP-Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies for each. Same risk classification, live on your fleet in minutes.

Enforce policy on every ABAP-ADT-API MCP-Server tool call.

Deterministic rules across all 127 ABAP-ADT-API MCP-Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

SECURE ABAP-ADT-API MCP-SERVER →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

ABAP-ADT-API MCP-Server

// TOOL MAP

// WHAT CAN GO WRONG

// RECOMMENDED RULES

// ALL 127 ABAP-ADT-API MCP-SERVER TOOLS

// FAQ