pg_copy_import
Generate COPY FROM command for importing data.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-copy-import.md
What pg_copy_import does on PostgreSQL MCP Server
AI agents use pg_copy_import to create or update resources in PostgreSQL MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PostgreSQL MCP Server environment.
Why pg_copy_import is rated Medium
pg_copy_import generates commands that create or modify data in the database by importing external data into tables. This is a Write operation as it produces reversible changes (imported data can be deleted). However, severity is elevated to 'high' due to the potential for large-scale data modification and the risk of corrupting tables if misused (e.g., importing to wrong table, incorrect data format).
From the tool's definition Tool name contains 'import' and description states 'Generate COPY FROM command for importing data.' COPY FROM is a PostgreSQL command that loads data into tables, modifying database contents.
Attacks that exploit this kind of access
The rule that runs pg_copy_import safely
PolicyLayer is an MCP gateway: it sits between your AI agents and PostgreSQL MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pg_copy_import, this is the rule to start with:
pg_copy_import 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.
The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_copy_import call is checked against it from then on.
Questions about pg_copy_import
Generate COPY FROM command for importing data. It is categorised as a Write tool in the PostgreSQL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_copy_import: 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 PostgreSQL MCP Server. Nothing to install.
pg_copy_import is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pg_copy_import 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.
Set action: deny in the PolicyLayer policy for pg_copy_import. 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.
pg_copy_import is provided by the PostgreSQL MCP Server MCP server (@neverinfamous/postgres-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on PostgreSQL MCP Server, and thousands of servers like it.
This server
Across the catalogue