csv_to_sql
Turn CSV/TSV into SQL: CREATE TABLE with inferred column types (integer/bigint, numeric, boolean, date, timestamp, varchar/text, NOT NULL where never empty, optional primary key) and batched INSERT statements with correct quoting and escaping for PostgreSQL, MySQL, SQLite or SQL Server. Up to 20,...
This record as markdown: /tools/com-it-scorptech-x402/csv-to-sql.md
What csv_to_sql does on ScorpTech x402 API
AI agents use csv_to_sql to create or update resources in ScorpTech x402 API, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScorpTech x402 API environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
csv | string | Yes | |
table | string | — | |
header | boolean | — | |
dialect | string | — | |
batchSize | integer | — | Rows per INSERT statement |
delimiter | string | — | |
primaryKey | string | — | Column to declare as PRIMARY KEY |
createTable | boolean | — |
Parameters from the server's own tool schema.
Why csv_to_sql is rated Medium
An AI agent can call csv_to_sql faster than any human can review: one bad instruction and it creates or modifies resources in ScorpTech x402 API by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs csv_to_sql safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For csv_to_sql, this is the rule to start with:
csv_to_sql 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 ScorpTech x402 API, apply this rule, and every csv_to_sql call is checked against it from then on.
Questions about csv_to_sql
Turn CSV/TSV into SQL: CREATE TABLE with inferred column types (integer/bigint, numeric, boolean, date, timestamp, varchar/text, NOT NULL where never empty, optional primary key) and batched INSERT statements with correct quoting and escaping for PostgreSQL, MySQL, SQLite or SQL Server. Up to 20,000 rows. POST JSON body {csv, table, dialect}. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/csv-to-sql. It is categorised as a Write tool in the ScorpTech x402 API MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
csv_to_sql accepts 8 parameters: csv, table, header, dialect, batchSize, delimiter, primaryKey, createTable. Required: csv. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for csv_to_sql: 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 ScorpTech x402 API. Nothing to install.
csv_to_sql 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 csv_to_sql 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 csv_to_sql. 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.
csv_to_sql is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue