csv_profile
Profile a CSV/TSV dataset: delimiter detection, row and column counts, per-column inferred type (integer, decimal, boolean, date, datetime, string), null/empty counts, distinct values, min/max/mean/median/std and percentiles for numbers, length stats and detected patterns (email, URL, phone) for ...
This record as markdown: /tools/com-it-scorptech-x402/csv-profile.md
What csv_profile does on ScorpTech x402 API
AI agents call csv_profile to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
csv | string | Yes | CSV / TSV text |
header | boolean | — | First row is a header |
delimiter | string | — | Force a delimiter (default: detect) |
topValues | integer | — |
Parameters from the server's own tool schema.
Why csv_profile is rated Low
Even though csv_profile only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs csv_profile 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_profile, this is the rule to start with:
csv_profile is read-only, so it stays allowed. 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_profile call is checked against it from then on.
Questions about csv_profile
Profile a CSV/TSV dataset: delimiter detection, row and column counts, per-column inferred type (integer, decimal, boolean, date, datetime, string), null/empty counts, distinct values, min/max/mean/median/std and percentiles for numbers, length stats and detected patterns (email, URL, phone) for text, top values, duplicate rows and data-quality warnings. Up to 50,000 rows. POST JSON body {csv}. Price: $0.003 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/csv-profile. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
csv_profile accepts 4 parameters: csv, header, delimiter, topValues. 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_profile: 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_profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the csv_profile 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_profile. 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_profile 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