High Risk →

runQuery

Runs a SQL query on the target system.

Part of the ABAP-ADT-API MCP-Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke runQuery to trigger processes or run actions in ABAP-ADT-API MCP-Server. 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.

runQuery 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.

mario-andreschak-mcp-abap-abap-adt-api.yaml
tools:
  runQuery:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full ABAP-ADT-API MCP-Server policy for all 127 tools.

Tool Name runQuery
Category Execute
Risk Level High

View all 127 tools →

Agents calling execute-class tools like runQuery 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.

runQuery is one of the high-risk operations in ABAP-ADT-API MCP-Server. 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 runQuery tool do? +

Runs a SQL query on the target system.. It is categorised as a Execute tool in the ABAP-ADT-API MCP-Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on runQuery? +

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

What risk level is runQuery? +

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

Can I rate-limit runQuery? +

Yes. Add a rate_limit block to the runQuery 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 runQuery completely? +

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

runQuery is provided by the ABAP-ADT-API MCP-Server MCP server (mario-andreschak/mcp-abap-abap-adt-api). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on ABAP-ADT-API MCP-Server

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.