High Risk →

query_database_jsonl

Execute a SQL query and return results in JSONL format.

How to control query_database_jsonl ↓

What query_database_jsonl does on Mcp Odbc

AI agents invoke query_database_jsonl to trigger actions in Mcp Odbc. 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.

High Risk

Why query_database_jsonl needs a policy

This tool executes arbitrary SQL queries against a database. While the name implies read-only queries, SQL execution can include DML (INSERT, UPDATE, DELETE) or DDL (DROP, CREATE) statements depending on permissions and the query passed. The blast radius is critical because a misused or injected query could modify or destroy data across the entire connected DBMS.

From the tool's definition "Execute a SQL query" — the tool runs arbitrary SQL against a connected DBMS via ODBC

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

How to control query_database_jsonl

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_database_jsonl": {
      "limits": [
        {
          "counter": "query_database_jsonl_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

query_database_jsonl 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.

  1. Create a free account and register Mcp Odbc — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about query_database_jsonl

What does the query_database_jsonl tool do? +

Execute a SQL query and return results in JSONL format. It is categorised as a Execute tool in the Mcp Odbc 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_database_jsonl? +

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

What risk level is query_database_jsonl? +

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

Can I rate-limit query_database_jsonl? +

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

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

query_database_jsonl is provided by the Mcp Odbc MCP server (openlinksoftware/mcp-odbc-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Odbc tool call.

Start from Mcp Odbc, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

15 Mcp Odbc tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.