execute_query

THE RISK

High Risk

Why execute_query needs a policy

This tool runs arbitrary SQL queries against production data systems. While the description adds '(simulated)', the server context emphasizes 'real tenant data discovery' and 'production-ready' capability, suggesting actual data access. SQL execution is inherently an Execute category action—effects depend entirely on the query argument (SELECT, INSERT, UPDATE, DELETE, DROP).

From the tool's definition Tool name is 'execute_query' and description states 'Execute a SQL query against Datasphere data'. The verb 'Execute' combined with 'SQL query' indicates code execution capability.

Documented attack patterns abuse exactly the kind of access execute_query gives an agent:

POLICY

How to control execute_query

PolicyLayer is an MCP gateway — it sits between your AI agents and SAP Datasphere MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_query:

policy.json

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

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

Create a free account and register SAP Datasphere MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More SAP Datasphere MCP Server tools

Execute query_analytical_data Execute OData queries on analytical models to retrieve aggregated data with dimensions and Execute query_relational_entity Execute OData queries on relational entities for ETL data extraction. Supports large batch Read get_analytical_metadata Retrieve CSDL metadata for analytical consumption of a specific asset. Returns analytical Read get_analytical_model Get the OData service document and metadata for a specific analytical model. Returns entit Read get_analytical_service_document Get the OData service document for a specific analytical asset. Returns the service root w Read get_asset_variables Retrieve input parameters/variables and filter-capability annotations declared in the ODat Read get_available_scopes List available OAuth2 scopes for the current user, showing which scopes are granted and wh Read get_catalog_metadata Get CSDL metadata for the SAP Datasphere catalog service. Retrieves the OData metadata doc

All 31 SAP Datasphere MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in SAP Datasphere MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about execute_query

What does the execute_query tool do? +

Execute a SQL query against Datasphere data (simulated). It is categorised as a Execute tool in the SAP Datasphere 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 execute_query? +

Register the SAP Datasphere MCP Server MCP server in PolicyLayer and add a rule for execute_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 Datasphere MCP Server. Nothing to install.

What risk level is execute_query? +

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

Can I rate-limit execute_query? +

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

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

execute_query is provided by the SAP Datasphere MCP Server MCP server (mariodefelipe/sap-datasphere-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SAP Datasphere MCP Server tool call.

Start from SAP Datasphere MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →