csv_json_convert
CSV <-> JSON Converter — Convert CSV text to a JSON array of row objects, or a JSON array of flat objects back to CSV text.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/csv-json-convert.md
What csv_json_convert does on Gateway
AI agents use csv_json_convert to create or update resources in Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gateway environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
csv | string | — | CSV text (direction=csv_to_json) |
records | array | — | JSON array of flat objects (direction=json_to_csv) |
delimiter | string | — | Single-character field delimiter (default ',') |
direction | string | Yes | csv_to_json | json_to_csv |
Parameters from the server's own tool schema.
Why csv_json_convert is rated Medium
This tool transforms data from one format to another without executing code, querying external systems, or causing irreversible deletion. Format conversion and data restructuring are Write-class operations. Severity is low because the tool operates on the data passed to it with no side effects on external systems, no financial impact, and easily reversible results.
From the tool's definition Tool converts between CSV and JSON formats, transforming data structure and potentially modifying output format.
Attacks that exploit this kind of access
The rule that runs csv_json_convert 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_json_convert, this is the rule to start with:
csv_json_convert 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 Gateway, apply this rule, and every csv_json_convert call is checked against it from then on.
Questions about csv_json_convert
CSV <-> JSON Converter — Convert CSV text to a JSON array of row objects, or a JSON array of flat objects back to CSV text. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
csv_json_convert accepts 4 parameters: csv, records, delimiter, direction. Required: direction. 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_json_convert: 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_json_convert 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_json_convert 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_json_convert. 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_json_convert 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