query_table · SingleStore MCP Server MCP: Risk & Policy

WHAT IT DOES

What query_table does on SingleStore MCP Server

AI agents invoke query_table to trigger actions in SingleStore MCP Server. 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_table needs a policy

While the tool may be intended for SELECT queries, 'execute a query' is broad enough to include DML/DDL statements (INSERT, UPDATE, DELETE, DROP). Sibling tools include a separate 'run_read_query' which suggests this tool may permit write or destructive queries. The most severe applicable category for arbitrary query execution is Execute, with high severity due to potential for data modification or destruction.

From the tool's definition "Execute a query on a table" — the description uses 'execute' and 'query', implying arbitrary SQL execution rather than a constrained read-only operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query_table Rate-limited

query_table 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_table": {
      "limits": [
        {
          "counter": "query_table_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 SingleStore MCP Server, so you can run agents against it safely.

FAQ

Questions about query_table

What does the query_table tool do? +

Execute a query on a table. It is categorised as a Execute tool in the SingleStore 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 query_table? +

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

What risk level is query_table? +

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

Can I rate-limit query_table? +

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

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

query_table is provided by the SingleStore MCP Server MCP server (madhukarkumar/singlestore-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.