AI agents call read_query to retrieve information from StarRocks MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the naming convention 'read_query' paired with the server's stated purpose of 'database exploration' indicates this tool executes SELECT-like queries for data retrieval without modification.
From the tool's definition Tool name 'read_query' combined with server description stating 'SQL execution and database exploration' indicates a data retrieval function. The 'read_' prefix strongly suggests read-only operations.
Documented attack patterns abuse exactly the kind of access read_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and StarRocks MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for read_query:
{
"version": "1",
"default": "deny",
"tools": {
"read_query": {}
}
}read_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
read_query. It is categorised as a Read tool in the StarRocks MCP Server MCP Server, which means it retrieves data without modifying state.
Register the StarRocks MCP Server 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 StarRocks MCP Server. Nothing to install.
read_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
read_query is provided by the StarRocks MCP Server MCP server (starrocks/mcp-server-starrocks). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 StarRocks MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 StarRocks MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.