Low Risk

get_sql

Returns the generated SQL for a given query without executing it.

How to control get_sql ↓

What get_sql does on Cube Js MCP Server

AI agents call get_sql to retrieve information from Cube Js MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_sql needs a policy

get_sql retrieves and displays SQL query strings generated by Cube.js without executing them or modifying any data. This is a read-only introspection capability with no side effects. Users can examine query logic but cannot trigger database operations, making it a low-severity Read tool suitable for understanding query generation and debugging.

From the tool's definition Tool returns generated SQL 'without executing it' - explicitly non-executable, purely informational retrieval

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

How to control get_sql

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_sql": {}
  }
}

get_sql is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Cube Js MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_sql

What does the get_sql tool do? +

Returns the generated SQL for a given query without executing it. It is categorised as a Read tool in the Cube Js MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_sql? +

Register the Cube Js MCP Server MCP server in PolicyLayer and add a rule for get_sql: 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 Cube Js MCP Server. Nothing to install.

What risk level is get_sql? +

get_sql is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_sql? +

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

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

get_sql is provided by the Cube Js MCP Server MCP server (zsembek/cube.js-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Cube Js MCP Server tool call.

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

Free to start. No card required.

10 Cube Js MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.