csv_profile
CSV Column-Stats Profiler — Per-column count/nulls/distinct/min/max/mean profile of a CSV (a column is numeric only if every non-null value parses as a number).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/csv-profile.md
What csv_profile does on Gateway
AI agents call csv_profile to retrieve information from Gateway 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 text (header row required) |
delimiter | string | — | Single-character field delimiter (default ',') |
Parameters from the server's own tool schema.
Why csv_profile is rated Low
This tool retrieves and analyzes metadata about a CSV file's structure and statistics without modifying, deleting, or executing any operations. It is a pure read operation that computes descriptive statistics on existing data. The narrow scope and lack of side effects warrant low severity.
From the tool's definition Tool performs profiling and statistical analysis of CSV columns: 'count/nulls/distinct/min/max/mean profile'. No modification, deletion, or execution of external operations occurs. Data retrieval and computation only.
Risk signalsBulk/mass operation — affects multiple targets
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 Gateway, 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 Gateway, apply this rule, and every csv_profile call is checked against it from then on.
Questions about csv_profile
CSV Column-Stats Profiler — Per-column count/nulls/distinct/min/max/mean profile of a CSV (a column is numeric only if every non-null value parses as a number). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
csv_profile accepts 2 parameters: csv, delimiter. Required: csv. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway 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 Gateway. 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 Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue