Import data from a CSV file into a database table. Creates the table if it doesn
AI agents use import_csv to create or update resources in MCP Database Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Database Server environment.
The tool creates or modifies database tables by importing CSV data. This is reversible (data can be updated or removed later), making it a Write operation rather than Destructive. Severity is medium because an agent misusing this could overwrite existing tables or corrupt data schemas, but the impact is limited to a single database and reversible through standard database operations.
From the tool's definition Tool description states it 'Import[s] data from a CSV file into a database table' and 'Creates the table if it doesn[t exist]', indicating data creation and modification operations.
Attacks that exploit this kind of access
Import data from a CSV file into a database table. Creates the table if it doesn. It is categorised as a Write tool in the MCP Database Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Database Server MCP server in PolicyLayer and add a rule for import_csv: 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 MCP Database Server. Nothing to install.
import_csv 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 import_csv 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 import_csv. 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.
import_csv is provided by the MCP Database Server MCP server (jakubbuskiewicz/mcp-test). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →