run_query

A execute tool on the Sap Btp Destination MCP server.

SERVERSap Btp Destination SOURCEfacusada/mcp-btp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/facusada-mcp-btp/run-query.md

WHAT IT DOES

What run_query does on Sap Btp Destination

AI agents invoke run_query to trigger actions in Sap Btp Destination. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why run_query is rated High

The tool name 'run_query' combined with context (SAP BTP, destinations, financial sibling tools) indicates code or command execution rather than read-only retrieval. Query execution against enterprise systems can trigger side effects, modify state, or access sensitive data depending on what the destination targets.

From the tool's definition Tool name 'run_query' in a SAP BTP Destination server context suggests execution of queries. Combined with sibling tools like 'call_destination' and 'add_expense' indicating financial/operational capabilities, and the fact that description is empty (limiting…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_query safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sap Btp Destination, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_query, this is the rule to start with:

run_query Rate-limited

run_query stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_query": {
      "limits": [
        {
          "counter": "run_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sap Btp Destination, apply this rule, and every run_query call is checked against it from then on.

FAQ

Questions about run_query

What does the run_query tool do? +

run_query is a execute tool on the Sap Btp Destination MCP server. It is categorised as a Execute tool in the Sap Btp Destination MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_query? +

Register the Sap Btp Destination MCP server in PolicyLayer and add a rule for run_query: 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 Sap Btp Destination. Nothing to install.

What risk level is run_query? +

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

Can I rate-limit run_query? +

Yes. Add a rate_limit block to the run_query 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.

How do I block run_query completely? +

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

run_query is provided by the Sap Btp Destination MCP server (facusada/mcp-btp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sap Btp Destination, and thousands of servers like it.

This server

All 36 Sap Btp Destination tools → High-risk tools on this server →

Across the catalogue

run on 0sec →aroflo_query_zone on AroFlo MCP →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →