query

Execute a read-only SQL query (SELECT, SHOW, DESCRIBE) using Trino SQL dialect with Treasure Data UDFs. For better performance on large tables, use td_interval(time, \

ServerTreasure Data MCP Server
CategoryRead

How to control query ↓

WHAT IT DOES

What query does on Treasure Data MCP Server

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

THE RISK

Low Risk

Why query needs a policy

This tool is restricted to read-only SQL operations (SELECT, SHOW, DESCRIBE). It cannot create, modify, delete, or execute arbitrary code—only retrieve and inspect data. The read-only constraint and explicit mention of supported query types place it firmly in the Read category with low severity risk.

From the tool's definition Tool name is 'query' and description explicitly states 'Execute a read-only SQL query (SELECT, SHOW, DESCRIBE)' with no modification or deletion capabilities mentioned.

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

POLICY

How to control query

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query": {}
  }
}

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

Create a free account and register Treasure Data 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.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Treasure Data MCP Server tools

Destructive execute Execute write operations (UPDATE, DELETE, INSERT, etc.) when enable_updates=true Destructive kill_attempt Request cancellation of a running attempt Execute retry_attempt Retry a specific failed attempt with resume capabilities Execute retry_session Retry a failed session from the beginning or a specific task Write use_database Switch the current database context for subsequent queries Read current_database Get the current database context being used for queries Read describe_table Get column information for a specific table Read get_attempt_tasks List all tasks within an attempt with their execution status

All 23 Treasure Data MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about query

What does the query tool do? +

Execute a read-only SQL query (SELECT, SHOW, DESCRIBE) using Trino SQL dialect with Treasure Data UDFs. For better performance on large tables, use td_interval(time, \. It is categorised as a Read tool in the Treasure Data MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query? +

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

What risk level is query? +

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

Can I rate-limit query? +

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

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

query is provided by the Treasure Data MCP Server MCP server (treasure-data/td-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 Treasure Data MCP Server tool call.

Start from Treasure Data 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 →

Free to start. No card required.

23 Treasure Data MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.