High Risk →

SAPDiagnose

Run diagnostics on ABAP objects: syntax check, ABAP unit tests, and ATC (ABAP Test Cockpit) code quality checks.

Part of the Arc 1 MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

arc-1 Execute Risk 3/5

AI agents invoke SAPDiagnose to trigger processes or run actions in Arc 1. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

SAPDiagnose can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

arc-1.yaml
tools:
  SAPDiagnose:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Arc 1 policy for all 11 tools.

Tool Name SAPDiagnose
Category Execute
MCP Server Arc 1 MCP Server
Risk Level High

View all 11 tools →

Agents calling execute-class tools like SAPDiagnose have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

SAPDiagnose is one of the high-risk operations in Arc 1. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the SAPDiagnose tool do? +

Run diagnostics on ABAP objects: syntax check, ABAP unit tests, and ATC (ABAP Test Cockpit) code quality checks.. It is categorised as a Execute tool in the Arc 1 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on SAPDiagnose? +

Add a rule in your Intercept YAML policy under the tools section for SAPDiagnose. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Arc 1 MCP server.

What risk level is SAPDiagnose? +

SAPDiagnose is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit SAPDiagnose? +

Yes. Add a rate_limit block to the SAPDiagnose rule in your Intercept 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 SAPDiagnose completely? +

Set action: deny in the Intercept policy for SAPDiagnose. 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 SAPDiagnose? +

SAPDiagnose is provided by the Arc 1 MCP server (arc-1). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Arc 1

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.