List the API release-state contracts the system defines — the catalog used to classify released objects (e.g. USE_IN_KEY_USER_APPS = C1, ADD_CUSTOM_FIELDS = C0), each with its compatibility-contract description. This is the released-API classification catalog, not a per-object enumeration (object...
AI agents call adt_list_released_apis 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 purely retrieves and enumerates metadata about SAP's API release-state classifications (e.g., C0, C1 contracts). It has no side effects—it queries a reference catalog, not business data. It does not create, modify, delete, or execute any operations.
From the tool's definition Tool description: 'List the API release-state contracts the system defines — the catalog used to classify released objects'. The operation is explicitly a list/catalog query operation with no mutations.
Documented attack patterns abuse exactly the kind of access adt_list_released_apis 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_released_apis:
{
"version": "1",
"default": "deny",
"tools": {
"adt_list_released_apis": {}
}
} adt_list_released_apis 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 the API release-state contracts the system defines — the catalog used to classify released objects (e.g. USE_IN_KEY_USER_APPS = C1, ADD_CUSTOM_FIELDS = C0), each with its compatibility-contract description. This is the released-API classification catalog, not a per-object enumeration (object-level released-API listing requires the release-dependent RIS search facet). Backed by repository/informationsystem/releasestates. 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_released_apis: 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_released_apis 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_released_apis 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_released_apis. 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_released_apis 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.