Create a new ABAP object in a package. Supported types: program, class, interface, include, functiongroup, function, cds, accesscontrol, metadataext, behaviordef, messageclass. Refused under read-only mode.
AI agents use adt_create_object to create or update resources in Claude For Abap — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude For Abap environment.
Creating ABAP objects in SAP is a reversible write operation that modifies the system state by adding new code/configuration artifacts to packages. This is categorized as Write rather than Execute because the tool's primary function is object creation/composition rather than triggering arbitrary computation or code execution.
From the tool's definition Tool description states 'Create a new ABAP object in a package' and explicitly lists supported creation types (program, class, interface, include, functiongroup, function, cds, accesscontrol, metadataext, behaviordef, messageclass).
Documented attack patterns abuse exactly the kind of access adt_create_object 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_create_object:
{
"version": "1",
"default": "deny",
"tools": {
"adt_create_object": {
"limits": [
{
"counter": "adt_create_object_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}adt_create_object 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.
Free to start. No card required.
Create a new ABAP object in a package. Supported types: program, class, interface, include, functiongroup, function, cds, accesscontrol, metadataext, behaviordef, messageclass. Refused under read-only mode. 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.
Register the Claude For Abap MCP server in PolicyLayer and add a rule for adt_create_object: 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_create_object is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the adt_create_object 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_create_object. 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_create_object 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.