run_readonly_query · OpenLink MCP Server for ODBC MCP

WHAT IT DOES

What run_readonly_query does on OpenLink MCP Server for ODBC

AI agents invoke run_readonly_query 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 run_readonly_query needs a policy

Although constrained to SELECT/WITH (read-only), the tool actively executes SQL against an ODBC-connected database, making it an Execute action. The read-only constraint reduces severity, but misuse could still expose sensitive data across any ODBC-accessible database. Severity is medium due to potential for broad data exfiltration across schemas.

From the tool's definition 'Run a read-only SELECT/WITH SQL query against the configured ODBC database' — executes SQL queries against an external database system

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_readonly_query Rate-limited

run_readonly_query 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": {
    "run_readonly_query": {
      "limits": [
        {
          "counter": "run_readonly_query_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 run_readonly_query

What does the run_readonly_query tool do? +

Run a read-only SELECT/WITH SQL query against the configured ODBC database. Results are row-limited by default. Use all_rows=true to return all matching rows. 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 run_readonly_query? +

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

What risk level is run_readonly_query? +

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

Can I rate-limit run_readonly_query? +

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

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

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