query_database_md · OpenLink MCP Server for ODBC MCP

WHAT IT DOES

What query_database_md does on OpenLink MCP Server for ODBC

AI agents invoke query_database_md to trigger actions in OpenLink MCP Server for 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.

WHY IT NEEDS A POLICY

Why query_database_md needs a policy

The tool executes SQL queries, which can include not only SELECT statements but potentially DML/DDL (INSERT, UPDATE, DELETE, DROP) depending on the connection permissions. Since the tool description does not restrict to read-only queries (unlike 'export_readonly_query' which implies read-only), it could be used to modify or destroy data.

From the tool's definition "Execute a SQL query" — the tool runs arbitrary SQL against an ODBC-accessible database and returns results.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

query_database_md Rate-limited

query_database_md 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_database_md": {
      "limits": [
        {
          "counter": "query_database_md_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 OpenLink MCP Server for ODBC, so you can run agents against it safely.

FAQ

Questions about query_database_md

What does the query_database_md tool do? +

Execute a SQL query and return results in MD format. It is categorised as a Execute tool in the OpenLink MCP Server for 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_md? +

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

What risk level is query_database_md? +

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

Can I rate-limit query_database_md? +

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

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

query_database_md is provided by the OpenLink MCP Server for ODBC MCP server (pvsmark/pvs-odbc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

query_database_md is one line of OpenLink MCP Server for ODBC's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →