query_data_cube · Imply Druid MCP: Risk & Policy

WHAT IT DOES

What query_data_cube does on Imply Druid

AI agents invoke query_data_cube to trigger actions in Imply Druid. 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.

WHY IT NEEDS A POLICY

Why query_data_cube needs a policy

Despite the server being described as 'read-only', this tool executes SQL queries, which falls under Execute. Arbitrary SQL execution carries high risk as queries could be resource-intensive, expose sensitive data, or (depending on enforcement) include destructive statements. The blast radius is high given it operates against a live Druid/Imply database.

From the tool's definition "Execute SQL query against a data cube" — the tool actively runs SQL queries against a database system

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query_data_cube Rate-limited

query_data_cube 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": {
    "query_data_cube": {
      "limits": [
        {
          "counter": "query_data_cube_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Imply Druid, so you can run agents against it safely.

FAQ

Questions about query_data_cube

What does the query_data_cube tool do? +

Execute SQL query against a data cube (Pivot). Use. It is categorised as a Execute tool in the Imply Druid MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on query_data_cube? +

Register the Imply Druid MCP server in PolicyLayer and add a rule for query_data_cube: 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 Imply Druid. Nothing to install.

What risk level is query_data_cube? +

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

Can I rate-limit query_data_cube? +

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

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

query_data_cube is provided by the Imply Druid MCP server (yeongbin-hwang/imply-druid-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.