export_readonly_query · OpenLink MCP Server for ODBC MCP

WHAT IT DOES

What export_readonly_query does on OpenLink MCP Server for ODBC

AI agents use export_readonly_query to create or update resources in OpenLink MCP Server for ODBC — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenLink MCP Server for ODBC environment.

WHY IT NEEDS A POLICY

Why export_readonly_query needs a policy

Although the underlying database operation (SELECT/WITH) is read-only and would normally be classified as 'Read', the export mechanism creates or modifies files on the local system. This side effect of persisting data to disk qualifies as a Write operation.

From the tool's definition Tool description states 'Export a read-only SELECT/WITH query result to a local file.' The act of writing query results to a local file constitutes data creation/modification on the file system, even though the database query itself is read-only.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_readonly_query Rate-limited

export_readonly_query stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_readonly_query": {
      "limits": [
        {
          "counter": "export_readonly_query_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 export_readonly_query

What does the export_readonly_query tool do? +

Export a read-only SELECT/WITH query result to a local file. Rows are not returned to the LLM context. It is categorised as a Write tool in the OpenLink MCP Server for ODBC MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on export_readonly_query? +

Register the OpenLink MCP Server for ODBC MCP server in PolicyLayer and add a rule for export_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 export_readonly_query? +

export_readonly_query is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit export_readonly_query? +

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

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

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