This record as markdown: /tools/io-github-devopam-mcpg/copy-table-between-databases.md
What copy_table_between_databases does on Mcpg
AI agents use copy_table_between_databases to create or update resources in Mcpg, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcpg environment.
Why copy_table_between_databases is rated Medium
Copying tables between databases is a write operation that modifies the target database by adding or replacing data. While reversible, it poses a high severity risk because an agent could copy sensitive data to unintended locations, corrupt data through schema mismatches, or impact performance by copying large tables without authorization.
From the tool's definition Tool name 'copy_table_between_databases' indicates it creates or duplicates table data from one database to another. The empty description limits certainty, but the operation is inherently reversible (copied data can be removed).
Attacks that exploit this kind of access
The rule that runs copy_table_between_databases safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For copy_table_between_databases, this is the rule to start with:
copy_table_between_databases 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 Mcpg, apply this rule, and every copy_table_between_databases call is checked against it from then on.
Questions about copy_table_between_databases
copy_table_between_databases is a write tool on the Mcpg MCP server. It is categorised as a Write tool in the Mcpg MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcpg MCP server in PolicyLayer and add a rule for copy_table_between_databases: 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 Mcpg. Nothing to install.
copy_table_between_databases 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 copy_table_between_databases 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 copy_table_between_databases. 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.
copy_table_between_databases is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcpg, and thousands of servers like it.
This server
Across the catalogue