File a bug or enhancement about a sap-adt-mcp TOOL back to the maintainer. The report is redacted (hosts, users, passwords, IPs, emails stripped), de-duplicated, and becomes a GitHub issue. Use this for defects the automatic crash reporter cannot see: wrong data in an otherwise-successful respons...
AI agents use adt_report_issue 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.
This tool creates a new GitHub issue by filing a bug report. Creation of records is a Write operation. The severity is low because: (1) the report is redacted to remove sensitive data, (2) the impact is limited to the MCP tool maintainer's issue tracker, (3) issues are not financial or destructive operations, and (4) misuse would only result in spurious or duplicate GitHub issues, which have minimal blast radius.
From the tool's definition Tool description states it 'File[s] a bug or enhancement' and 'becomes a GitHub issue', indicating creation of a new record (GitHub issue). The action is reversible (issues can be closed/deleted).
Documented attack patterns abuse exactly the kind of access adt_report_issue 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_report_issue:
{
"version": "1",
"default": "deny",
"tools": {
"adt_report_issue": {
"limits": [
{
"counter": "adt_report_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} adt_report_issue 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.
File a bug or enhancement about a sap-adt-mcp TOOL back to the maintainer. The report is redacted (hosts, users, passwords, IPs, emails stripped), de-duplicated, and becomes a GitHub issue. Use this for defects the automatic crash reporter cannot see: wrong data in an otherwise-successful response, a parameter that is silently ignored, or a missing capability. Do NOT use it for problems in the user. 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_report_issue: 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_report_issue 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_report_issue 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_report_issue. 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_report_issue 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.