export_table_to_path · Duckdb MCP: Risk & Policy

WHAT IT DOES

What export_table_to_path does on Duckdb

AI agents use export_table_to_path to create or update resources in Duckdb — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Duckdb environment.

WHY IT NEEDS A POLICY

Why export_table_to_path needs a policy

Exporting data to a file path is a Write operation: it creates or modifies files (reversible, no financial impact, not destructive deletion, not code execution). Severity is medium because uncontrolled file exports could overwrite existing files, leak sensitive data to unintended locations, or fill disk space, but the operation remains reversible and scoped to file I/O without arbitrary code execution or…

From the tool's definition Tool name 'export_table_to_path' and description 'Export a table to a file' indicate data serialization and file system write operations. The tool creates or modifies files on the file system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_table_to_path Rate-limited

export_table_to_path 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_table_to_path": {
      "limits": [
        {
          "counter": "export_table_to_path_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 Duckdb, so you can run agents against it safely.

FAQ

Questions about export_table_to_path

What does the export_table_to_path tool do? +

Export a table to a file. It is categorised as a Write tool in the Duckdb 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_table_to_path? +

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

What risk level is export_table_to_path? +

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

Can I rate-limit export_table_to_path? +

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

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

export_table_to_path is provided by the Duckdb MCP server (synehq/mcp-server-duckdb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.