export_query · General-Purpose MCP Database Server MCP

WHAT IT DOES

What export_query does on General-Purpose MCP Database Server

AI agents invoke export_query to trigger actions in General-Purpose MCP Database 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.

WHY IT NEEDS A POLICY

Why export_query needs a policy

The description is empty, so classification relies on the tool name and server context. 'export_query' likely executes a SQL query and exports the results to an external destination or file. Sibling tools like 'read_query' and 'write_query' suggest this tool runs a query (Execute category). Data export could expose sensitive information at scale, warranting high severity.

From the tool's definition Tool name 'export_query' on a server that provides 'full PostgreSQL database access, including tools for query execution' and 'data export'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_query Rate-limited

export_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": {
    "export_query": {
      "limits": [
        {
          "counter": "export_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 General-Purpose MCP Database Server, so you can run agents against it safely.

FAQ

Questions about export_query

What does the export_query tool do? +

export_query. It is categorised as a Execute tool in the General-Purpose MCP Database Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on export_query? +

Register the General-Purpose MCP Database Server MCP server in PolicyLayer and add a rule for export_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 General-Purpose MCP Database Server. Nothing to install.

What risk level is export_query? +

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

Can I rate-limit export_query? +

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

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

export_query is provided by the General-Purpose MCP Database Server MCP server (miekxd/general-database-fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.