execute_query_post

THE RISK

High Risk

Why execute_query_post needs a policy

This tool runs queries against a Cube.js analytics system. While the queries themselves are data retrieval focused (Read-like), the 'execute_query' pattern with POST method and support for complex queries means an AI could craft malicious queries (e.g., expensive aggregations, denial-of-service queries, or extraction of unauthorized data at scale).

From the tool's definition Tool name 'execute_query_post' and description states it 'Executes a query against the Cube.js API'. The verb 'Executes' combined with ability to run 'complex queries' against an analytics platform indicates code/query execution capability.

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

POLICY

How to control execute_query_post

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 execute_query_post:

policy.json

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

execute_query_post 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 Cube Js 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 Cube Js MCP Server tools

Execute execute_query execute_query Execute refresh Trigger a refresh for the given query (POST /refresh). Execute scheduled_refresh Trigger scheduled refresh (POST /refresh/schedule or similar). Execute raw_request Generic request tool to call arbitrary Cube.js REST endpoints. Execute refresh_pre_aggregations Refresh pre-aggregations (POST /pre-aggregations/refresh). Read check_health Checks the health status of the Cube.js server. Read get_schema Get the schema representation from Cube.js (GET /schema). Read get_sql Returns the generated SQL for a given query without executing it.

All 10 Cube Js 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 Cube Js 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_post

What does the execute_query_post tool do? +

Executes a query against the Cube.js API using POST method (recommended for complex queries). It is categorised as a Execute tool in the Cube Js 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_post? +

Register the Cube Js MCP Server MCP server in PolicyLayer and add a rule for execute_query_post: 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 execute_query_post? +

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

Can I rate-limit execute_query_post? +

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

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

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

CHECK YOUR STACK →