Execute SQL queries on TimescaleDB Cloud
AI agents invoke timescale_query to trigger actions in TigerData-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.
This tool executes arbitrary SQL queries against a cloud PostgreSQL/TimescaleDB database. While the server description mentions 'run queries and pull information,' the tool itself allows any SQL, which could include SELECT (Read), INSERT/UPDATE (Write), DELETE/DROP (Destructive), or stored procedure calls (Execute).
From the tool's definition 'Execute SQL queries on TimescaleDB Cloud' — arbitrary SQL execution including potentially destructive DDL/DML statements
Attacks that exploit this kind of access
Execute SQL queries on TimescaleDB Cloud. It is categorised as a Execute tool in the TigerData-mcp-server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TigerData-mcp-server MCP server in PolicyLayer and add a rule for timescale_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 TigerData-mcp-server. Nothing to install.
timescale_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the timescale_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 timescale_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.
timescale_query is provided by the TigerData-mcp-server MCP server (thesurfingcoder/tigerdata-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →