read_query · StarTree MCP Server for Apache Pinot MCP

WHAT IT DOES

What read_query does on StarTree MCP Server for Apache Pinot

AI agents invoke read_query to trigger actions in StarTree MCP Server for Apache Pinot. 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.

THE RISK

High Risk

Why read_query needs a policy

Although the tool is described as executing SELECT queries (read-only), it actively runs code/queries on an external system rather than simply fetching predefined data. An AI agent could craft complex or expensive queries causing denial-of-service, data exfiltration at scale, or exposure of sensitive data. The word 'Execute' in the description confirms active query execution.

From the tool's definition "Execute a SELECT query on the Pinot database" — the tool runs arbitrary SQL queries against the database.

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

POLICY

How to control read_query

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

policy.json

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

read_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 StarTree MCP Server for Apache Pinot — 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 StarTree MCP Server for Apache Pinot tools

Destructive reset-table-segments Resets segments for a table (disable->wait->enable). Use Execute force_commit Force commit the current consuming segments Execute pause_consumption Pause consumption of a realtime table Execute rebalance-table Rebalances a table (reassign instances and segments) Execute reload_table_filters reload_table_filters Execute reload-table-segments Reload all segments for a table (applies config changes, can Execute resume_consumption Resume consumption of a realtime table Write add-index Adds a specified index type to one or more columns in a table

All 26 StarTree MCP Server for Apache Pinot 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 StarTree MCP Server for Apache Pinot → 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 read_query

What does the read_query tool do? +

Execute a SELECT query on the Pinot database. It is categorised as a Execute tool in the StarTree MCP Server for Apache Pinot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on read_query? +

Register the StarTree MCP Server for Apache Pinot MCP server in PolicyLayer and add a rule for read_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 StarTree MCP Server for Apache Pinot. Nothing to install.

What risk level is read_query? +

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

Can I rate-limit read_query? +

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

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

read_query is provided by the StarTree MCP Server for Apache Pinot MCP server (startreedata/mcp-pinot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every StarTree MCP Server for Apache Pinot tool call.

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

CHECK YOUR STACK →

Free to start. No card required.

26 StarTree MCP Server for Apache Pinot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.